Method and system for managing a pre-encoded media asset for immediate playback

ABSTRACT

A system is provided for managing a pre-encoded media asset for immediate playback. The system generates, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments. The generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, is communicated to a media player of the first client device via a content delivery system for an immediate playback of a pre-encoded media asset. The system assigns a unique SID to the first client device to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request. A final pre-encoded media asset manifest is generated upon a receipt of the subsequent manifest request from the first client device based on a defined criterion.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application is a Continuation-in-part of U.S. patent application Ser. No. 17/094,319, filed on Nov. 10, 2020, which is a continuation of U.S. patent application Ser. No. 16/234,870, filed on Dec. 28, 2018, which is further a Continuation-in-part of U.S. patent application Ser. No. 15/396,475, filed on Dec. 31, 2016, and claims priority to, and the benefit from U.S. Provisional Application Ser. No. 62/699,131, filed Jul. 17, 2018.

This application also makes reference to:

U.S. application Ser. No. 15/988,241, filed on May 24, 2018, now U.S. Pat. No. 10,924,804; U.S. application Ser. No. 16/229,310, filed on Dec. 21, 2018, now U.S. Pat. No. 11,019,384; U.S. application Ser. No. 16/229,497, filed on Dec. 21, 2018; U.S. application Ser. No. 16/235,445, filed on Dec. 28, 2018, now U.S. Pat. No. 10,992,973; and U.S. application Ser. No. 16/236,673, filed on Dec. 31, 2018, now U.S. Pat. No. 10,856,016.

Each of the above referenced patent applications is hereby incorporated herein by reference in its entirety.

FIELD OF TECHNOLOGY

Certain embodiments of the disclosure relate to a television content packaging and distribution system. More specifically, certain embodiments of the disclosure relate to a method and system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback.

BACKGROUND

Recent advancements in the field of television content packaging and distribution systems have led to a massive development of numerous technologies and broadcasting platforms that are revolutionizing the way consumer devices access and playout media content. Usually, broadcasting platforms refer to the types of networks that are used to deliver the media content to the consumers. Currently, the broadcasting platforms, such as analog terrestrial broadcast, digital terrestrial broadcast, direct-to-home satellite broadcast, cable, Internet Protocol (IP), and over-the-top television (OTT), compete and strive to increase their appeal by gaining and retaining the audience viewing the media content.

Modern streaming protocols, such as HTTP Live Streaming (HLS) and Dynamic Adaptive Streaming over HTTP (DASH), are implemented to support streaming of various live content services, such as DIRECTV NOW℠, SLING TV℠ and PLAYSTAYION™ VUE, to consumer devices. Due to dissemination of such modern streaming protocols in the television, radio, and broadcasting sector, it is evident that the success of broadcasting will be dependent on the ability of the network provider to gain access to the content that consumers demand, and to differentiate their offering from that of incumbent broadcasters or find breakthrough modes of media content delivery.

Existing systems for Server-Side Ad Insertion (SSAI) support live streaming and make decisions to insert non-programing content in near real-time. However, for On-Demand streaming, such decisions to insert non-programing content are made upfront. Accordingly, amount of control the user can excerpt to influence what non-programming content is shown may get limited.

Further, leveraging the SSAI to insert the non-programming content into a Video On-Demand (VOD) manifest introduces delay in delivering the VOD manifest to a player of a client device, thus negatively affecting the viewer experience. Such a delay may be impacted by various factors, such as the number of advertisement breaks in the VOD content and use of multiple programmatic advertisement decision servers.

Various systems and methods are being implemented to manage such delays. One method may be to hide the delay (introduced by an advertisement insertion process) by playing a brand logo while the advertisement insertion process is being completed. However, such systems and methods fail to address the goal of making the first frame of the VOD content available to the viewer in minimal time. Other systems and methods are being implemented to treat the VOD asset as if it were a live stream. Accordingly, instead of inserting all the advertisements at the very beginning of the VOD manifest, the advertisements may be inserted as they are encountered in the timeline. However, such systems and methods introduce higher costs as the client session must be maintained for the complete duration of the VOD asset. Besides, the viewer experience may also get complicated as various play modes may not be supported without a significantly more complicated player-SSAI system integration.

Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present disclosure as set forth in the remainder of the present application with reference to the drawings.

BRIEF SUMMARY OF THE DISCLOSURE

Systems and/or methods are provided for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

These and other advantages, aspects and novel features of the present disclosure, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A is a block diagram that illustrates an exemplary system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure.

FIG. 1B is a block diagram that illustrates an exemplary dynamic ad/content insertion system (DACIS) for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, in accordance with an exemplary embodiment of the disclosure.

FIG. 1C is another block diagram that illustrates an exemplary system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback, in accordance with another exemplary embodiment of the disclosure.

FIG. 1D is a block diagram that illustrates an exemplary system for managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure.

FIG. 2 illustrates segmentation of live input streams and pre-encoded media assets for a first programming schedule for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content by the DACIS of FIG. 1B, in accordance with an exemplary embodiment of the disclosure.

FIG. 3 illustrates an exemplary scenario associated with publishing a disparate live media output stream by the DACIS of FIG. 1B, in accordance with an exemplary embodiment of the disclosure.

FIGS. 4A to 4D collectively depict a flowchart illustrating exemplary operations for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content by the DACIS of FIG. 1B, in accordance with an exemplary embodiment of the disclosure.

FIG. 5A is a conceptual diagram illustrating an example of a hardware implementation for the DACIS employing a processing system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, in accordance with an exemplary embodiment of the disclosure.

FIG. 5B is a conceptual diagram illustrating an example of a hardware implementation for the system employing a processing system for managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure.

FIG. 6A illustrates a first exemplary scenario associated with managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure.

FIG. 6B illustrates a second exemplary scenario associated with managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure.

FIG. 6C illustrates a third exemplary scenario associated with managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure.

FIGS. 7A to 7E collectively depict a flowchart illustrating exemplary operations for managing a pre-encoded media asset for immediate playback by the SSAI system of FIG. 1D, in accordance with an exemplary embodiment of the disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

Certain embodiments of the disclosure may be found in a method and system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback. Various embodiments of the disclosure provide a method and system that not only provide live channel offerings in cost-effective manner but also provide enhanced, intelligent, and personalized viewer experience to increase their appeal by retaining the audience viewing the media content. Additional embodiments of the disclosure provide a method and system for managing the pre-encoded media asset to allow a media player of a first client device to receive a first frame of media corresponding to the pre-encoded media asset for immediate playback, while also not incurring the cost of sustaining a client session for the entire duration of the pre-encoded media asset.

Modern streaming protocols, such as HLS and DASH, break media content into numerous small media content segments, typically less than 10 seconds in length. Further, the modern streaming protocols implement manifests that instruct a media player on what media content segment to retrieve and play next. The manifest may enlist the media segments that make up the full length of the media asset. The manifest may include information, based on which the media player at a consumer device may be able to determine the media segments. The manifest and/or media content segment may also include and/or specify additional information to facilitate a media player to transition smoothly between media content streams from different sources. The manifest may be used for creating a playlist of multiple media content files, or for interrupting media content with advertising and then resuming the media content.

Such modern streaming protocols support video-on-demand (VOD) assets and live content as well. The VOD assets prepared for distribution, for example Internet distribution, may have a sequence of short duration segments added to a manifest. The short duration segments may be separate physical files or pointers (real or to be calculated) to the short media content segments inside a larger file. On the other hand, in case of live content, new short content media segments are made available as soon as they are created. In some protocols, each new segment is added to a manifest while in others the media player is provided with information that may be utilized to calculate what the next live segment will be. In the latter case, a signal in the media content itself may be utilized to inform the player when to re-inspect or check the manifest for a change in media content. In live streaming, delivery of live content is supported by making available each new short media content segments as soon as such media content segments are generated. In some protocols, new media content segments may be added to the manifest, while in others, the media player calculates necessary information about the next live media content segments.

In accordance with various embodiments of the disclosure, a system is provided for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content. One or more processors in the system may be configured to receive a first manifest request from a first client device, wherein the first manifest request comprises one or more parameters. The one or more processors in the system may be further configured to determine a first additional content that comprises a customized first programming content and a targeted first non-programming content for the first client device based on the one or more parameters and the associated indexed metadata. The one or more processors in the system may be further configured to generate a first programming schedule for the first client device based on the selected one or more live input streams and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content. Accordingly, one or more live input stream manifests and/or one or more pre-encoded media asset manifests published in a content delivery network and associated indexed metadata may be selected based on the one or more parameters. The one or more processors in the system may be further configured to publish a first disparate live media output stream manifest for the first client device based on insertion of the selected one or more live input stream manifests and/or the one or more pre-encoded media asset manifests, the associated indexed metadata, and the determined first additional content in accordance with the first programming schedule generated for the first client device.

In accordance with another aspect of the disclosure, a system is provided for managing a pre-encoded media asset for immediate playback. One or more processors in the system may be configured to generate, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments. The one or more processors in the system may be further configured to communicate the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device via a content delivery system for an immediate playback of a pre-encoded media asset. The one or more processors in the system may be further configured to assign a unique session identifier (SID) to the first client device to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request. The one or more processors in the system may be further configured to generate a final pre-encoded media asset manifest upon a receipt of the subsequent manifest request from the first client device based on a defined criterion. The final pre-encoded media asset manifest may comprise remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters.

FIG. 1A is a block diagram that illustrates an exemplary system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback, in accordance with exemplary embodiments of the disclosure. Referring to FIG. 1A, the system 100A, comprises a media packaging and distribution system 102 that is communicatively coupled to published data sources 104 a, . . . , 104 n, Ad decisioning servers 106 a, . . . , 106 n, via a network 108 and/or other programmatic means. There are shown consumer devices 110 a, . . . , 110 n that are communicatively coupled to the network 108. The media packaging and distribution system 102 may comprise at least a DACIS 103, a Content Decisioning Service (CDS) 105, a Content Packaging and Distribution System (CPDS) 107, a stream selection service 142, and a repository of schedules, rights, and user preferences database 144. There are also shown source devices 118 communicatively coupled to the media packaging and distribution system 102 through the network 108. An external data source 120 is also provided, which is communicatively coupled to the media packaging and distribution system 102 through the network 108.

In accordance with another aspect of the disclosure, the DACIS 103 may include a server-side ad insertion (SSAI) system 109. As discussed in the present disclosure, the DACIS 103 corresponds to a system that is configured to dynamically insert targeted non-programming content (such as advertisements) and customized programming content (such as alternative programs) in a given manifest and generates a disparate per-client live media output stream. On the other hand, the SSAI system 109 corresponds to a system that is configured to only insert targeted non-programming content and/or non-scheduled programming content in the given manifest. Thus, in accordance with a first embodiment, as described above, the SSAI system 109 in FIG. 1A is illustrated as a subset of the DACIS 103 and may be implemented within the DACIS 103. Notwithstanding, the illustrated arrangement of the SSAI system 109 within the DACIS 103 in FIG. 1A should not be construed to be limiting. Another arrangement, in accordance with a second embodiment, may be implemented in the system 100C as illustrated in FIG. 1C, without any deviation from the scope of the disclosure. In accordance with the second embodiment, the SSAI system 109 may be implemented separately from the DACIS 103.

The media packaging and distribution system 102 may comprise suitable logic, circuitry, and interfaces that may be configured to execute code that handles media content comprising audio, video, images, metadata, manifests, and/or other data (embedded and/or externally referenced). The media content may include a video, an audio, a combination of audio and video presentations, and/or embedded or externally referenced metadata, a combination of multiple-audio, multiple-video, and/or embedded or externally referenced metadata. Accordingly, the media packaging and distribution system 102 publishes a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content.

In this regard, the media packaging and distribution system 102 may provide video programming services to viewers, usually for a subscription fee (such as pay television). The media packaging and distribution system 102 also handles distribution, for example, multicasting, unicasting, broadcasting, streaming, for one or more channels to be viewed on one or more of the plurality of consumer devices 110 a, . . . , 110 n.

The media packaging and distribution system 102 may be operated by an entity related to handling or distribution of media content, for example, a broadcast provider or operator, or a network provider or network operator. The entity related to handling or distribution of media content may also be referred to as a content owner, a distributor, a syndicator, a re-distributor, a content aggregator, a search, discovery, or cataloging service provider, or any other entity actively or passively involved with the distribution, cataloging, or referencing of complete or partial presentations of media content. Throughout this document, the terms broadcast provider or broadcast operator, and network provider or network operator may be utilized to refer to the entity related to handling or distribution of media content, interchangeably. The broadcast provider may handle a single channel or a plurality of channels, or one or more networks. The broadcast provider may be configured to distribute content via one or more platforms, for example, traditional over-the-air broadcast channels, radio, cable television networks, satellite communication networks, the Internet, and/or other content delivery networks (CDNs). In this regard, the broadcast provider may be configured to execute code that communicates linear video feeds (also referred to as a network television feed or broadcast feed) to the media packaging and distribution system 102. In a broadcast chain, the broadcast provider may receive actual content, for example, from a production studio, in one or more source formats. Examples of the one or more source formats may include, but are not limited to a tape file, or a live feed that may be further converted to a serial digital interface (SDI) video interface and/or on a high-definition SDI (HD-SDI) video interface for processing and playout. The broadcast provider may further process the content, such as insertion of graphics, closed captions, preparation of programming schedule, insertion of triggers, and the like, and provide final delivery by a broadcasting apparatus. The communicated linear video feed and the playout schedule may correspond to a channel, such as CNN channel that is broadcast to the media packaging and distribution system 102, via a communication network. The linear video feed may be broadcasted as a multi-program transport stream (MPTS) (also referred to as a live video feed) to the media packaging and distribution system 102, via the network 108. The broadcast provider may be owned by (or associated to) a broadcast provider or operator, a network provider or operator, or a content provider or operator.

The media packaging and distribution system 102 may receive the MPTS, which includes the signaling content and metadata, from the broadcast provider based on, for example, current society of cable telecommunication engineers (SCTE) standards (SCTE-35 and SCTE-224) to control web and regional blackouts, network end of day switching, and advertisement insertion. For example, the media packaging and distribution system 102 may be signaled for various blackout types with in-band SCTE-35 message. Further, the media packaging and distribution system 102 may receive program metadata that specifies certain events or operations, such as, for example, when to blackout shows. Examples of legacy distribution system that may be benefitted from the media packaging and distribution system 102 may include direct-broadcast satellite (DBS) providers, cable television (CATV) systems, and other wireline video providers and competitive local exchange carriers (CLECs) using, for example, IPTV.

The DACIS 103 may comprise suitable logic, circuitry, and interfaces that may be configured to leverage one-to-one scale of traditional SSAI systems to support custom programming content choices and not just targeted non-programming content. For example when the user selects to join a live stream, a content decisioning system, such as the CDS 105 could determine that, instead of joining the live stream for the last few minutes of a program prior to the start of the intended program, the user should instead be shown content more relevant to the user so as to prevent them from tuning away, e.g. show a personalized set of basketball highlights and ads to a user who likely joined the stream to watch a basketball game that is coming on next. The DACIS 103 replaces original content in the live stream prior to game start with user relevant content, such that upon its conclusion, the user is seamlessly presented the game.

The DACIS 103 may be further configured to, via a programming schedule or tag indicator in a disparate live media output stream manifest, be notified of one or more content graphical treatment opportunities within the media content. The DACIS 103 may be further configured to make required non-programing content calls on behalf of the plurality of consumer devices 110 a, . . . , 110 n. Accordingly, the DACIS 103 may provide the plurality of consumer devices 110 a, . . . , 110 n with information needed to execute the graphical treatment graphical content via a secure out-of-band channel between the DACIS 103 and the plurality of consumer devices 110 a, . . . , 110 n. In accordance with an embodiment, the DACIS 103 may be configured to include not showing non-programming content that a user of a consumer device may elected to skip or rated poorly in an earlier non-programming content break. Further, the DACIS 103 may enable the user to skip non-programming content as the user interacted with a previous non-programming content or made a purchase and the advertiser elected to sponsor the remainder of the programming content.

In accordance with an embodiment, the DACIS 103 may be configured to provide seamless failover between redundant disparate live media output streams for large events, thus improving reliability. In certain instances, some of the plurality of consumer devices 110 a, . . . , 110 n may support a primary and backup disparate live media output streams and are able to fail between them. In other instances, others of the plurality of consumer devices 110 a, . . . , 110 n may not support the primary and backup disparate live media output streams. In such instances, the consumer devices may attempt to join an alternative disparate live media output stream after occurrence of an event such as a device failure or crash. For such consumer devices, the DACIS 103 may be configured to monitor both the primary and backup disparate live media output streams, and if there is a failure, write the alternative disparate live media output stream into the disparate live media output stream manifest.

Each of the plurality of published data sources 104 a, . . . , 104 n may be coupled to one or more television networks and may comprise suitable logic, circuitry, and interfaces that may be configured to execute code that provides actual audiences for programs that were distributed. As illustrated in FIG. 1A, the plurality of published data sources 104 a, . . . , 104 n are coupled to the media packaging and distribution system 102 via the network 108 and configured to monitor audience drift to or away from a tuned channel airing a live media output stream. The plurality of published data sources 104 a, . . . , 104 n may provide actual audiences for programs to the indexing and storage system 116. An exemplary published data source may be Nielsen. Nielsen has the capability to determine when a viewer watches the same set of media items, for example, advertisements and/or promotional content, in programming data, such as an episode, in a live video feed within 3 days of original airing, and provide Nielsen “C3” credit. Another exemplary published data source may be a published database that provides ratings for a media item, such as gross rating point (GRP). The GRP is advertising or promotion impact measure for each advertising and/or promotional campaigns, known in the art. Other exemplary published data sources may also include direct/indirect access to other public or private data sources (persistent or ephemeral) through programmatic means.

The CDS 105 may comprise suitable logic, circuitry, and interfaces that may be configured to determine, upon request, which programming content (or partial programming content) to deliver back to the plurality of consumer devices 110 a, . . . , 110 n. Thus, the CDS 105 may be configured to insert additional content (including non-programming content) or replace existing content, according to one or more parameters provided by the plurality of consumer devices 110 a, . . . , 110 n and data stored in various external systems and/or databases.

The Ad decisioning servers 106 a, . . . , 106 n may comprise suitable logic, circuitry, and interfaces that may be configured to implement at least an advertisement decisioning component that may be used during a real-time content or advertisement placement activity, for example during dynamic ad insertion. The Ad decisioning servers 106 a, . . . , 106 n may further determine ad-load opportunity, based on targeting data from schedules, rights, and user preferences database.

For example, commercial or non-commercial advertisements may be dynamically inserted within program segments of the live input streams based on the detected upcoming indicator, such as an inbound trigger, a signaling point, and/or a signal in a pre-encoded media asset and/or a live input stream by the Ad decisioning servers 106 a, . . . , 106 n.

In an embodiment, the DACIS 103 may be generalized as a proxy between the plurality of consumer devices 110 a, . . . , 110 n and the Ad decisioning servers 106 a, . . . , 106 n. In one implementation, a request is sent from a consumer device to the DACIS 103. The DACIS 10 may call on of the Ad decisioning servers 106 a, . . . , 106 n to determine a set of non-programming content that may be inserted into the disparate live media output stream.

The CPDS 107 may comprise suitable logic, circuitry, and interfaces that may be configured to index programming content, which is prepared for usage by a system, such as the stream publishing engine 114. The CPDS 107 may further define metadata detailing various facets of the programming and/or non-programing content including duration, known locations and opportunities for programing and/or non-programing content insertion/replacement.

The network 108 may be any kind of network, or a combination of various networks, and it is shown illustrating exemplary communication that may occur between the Ad decisioning servers 106 a, . . . , 106 n and the media packaging and distribution system 102. For example, the network 108 may comprise one or more of a cable television network, the Internet, a satellite communication network, a wide area network (WAN), a medium area network (MAN), and a local area network (LAN). Although a network 108 is shown, the disclosure is not limited in this regard; accordingly, other exemplary modes may comprise uni-directional or bi-directional distribution, such as packet-radio, satellite. Furthermore, the network 108 is an exemplary embodiment of a distribution system.

The SSAI system 109 may comprise suitable logic, circuitry, and interfaces that may be configured to insert non-scheduled programming content and/or non-programming content, such as advertisements, into playback instructions associated with a video on-demand asset or a pre-encoded media asset in accordance with the modern web streaming protocols. The SSAI system 109 may enable the non-scheduled programming content and/or the non-programming content to be targeted to individual client devices while maintaining clean transitions between content, such as programming content segments of the pre-encoded media asset, and the non-scheduled programming content and/or the non-programming content while also obfuscating the non-programming content from being blocked.

The consumer devices 110 a, . . . , 110 n may refer to end-user devices or consumption devices where the content is played to be consumed by a user. The number of impressions of a media item, such as an advertisement and/or promotional media, on such plurality of consumer devices 110 a, . . . , 110 n determines the advertising impact or promotion impact and number of actual audiences achieved during campaigns. Examples of the consumer devices 110 a, . . . , 110 n may include, but are not limited to, connected TVs, connected TV with paired and/or connected devices (e.g., HDMI sticks, tablets), personal computer, smartphone, tablet, OTT set-top, or hybrid set-top, and second screen devices such as smartphones, tablets, game consoles, personal computers, set-top boxes, and embedded devices. The consumer devices 110 a, . . . , 110 n may further include process/system that may process the output for any means, regardless of the capability or intent to decode for media presentation, and on which the consumer may launch a web page, a web application, or a web service to view media content.

The source devices 118 may comprise suitable logic, circuitry, and interfaces that may be configured to communicate a live media feed or live input streams of a channel, such as an existing channel, to the media packaging and distribution system 102. In accordance with an embodiment, the live input streams of the channel may correspond to a broadcast feed. The source device 118 may be communicatively coupled to the network 108.

The external data source 120 may comprise suitable logic, circuitry, and interfaces that may be configured to execute code that handles retrieval and storage of audience data that corresponds to subscribers of the plurality of consumer devices 110 a, . . . , 110 n. The audience data may include demographics data, audience targeting data, trending data, device type data, device platform data, and content recognition-based data, such as automatic content recognition (ACR)-based data. The trending data may comprise information on what's trending in the social networks (or platforms), such as Twitter®, Facebook®, and the like. The trending data also comprises information on what's trending based on social engagement, such as number of likes or votes to a particular media item, or number of people watching a particular media item. The trending data may indicate an aggregate interest level of a number of users in the social networks for a particular media item. For example, a thousand or more shares, or likes by a number of users may indicate a highly popular media item.

The stream selection service 142 may comprise suitable logic, circuitry, and interfaces that may be configured to execute code that may be configured to provide a consumer device, for example, the consumer device 110 a, requesting to view the disparate live media output stream with a correct variant of disparate live media output stream, based on the geolocation and identification of the consumer device 110 a, along with data retrieved from the repository of schedules, rights, and user preferences database 144.

The repository of schedules, rights, and user preferences database 144 may comprise suitable logic, circuitry, and interfaces that may be configured to store the schedules for all source feeds, availability rights for all the content in the schedules, regional blackout zones for the various sports leagues, predefined location-based viewing preferences, individual client viewing preferences, and any viewing or transition rules provided by the stream owner operator.

In operation, in accordance with an aspect of the disclosure, upon receiving a first manifest request from a consumer device, the DACIS 103 may be configured to publish a manifest of a first disparate live media output stream for the consumer device. The first disparate live media output stream may be chosen by the DACIS 103, at the time of the first manifest request, to best target a consumer device, according to a plurality of client-specific parameters. The plurality of client-specific parameters may comprise user preferences and identifiers, consumer device preferences and identifiers, and one or more rules/rights governed by geolocation data and current position of playback of a first disparate live media output stream at the consumer device. The first disparate live media output stream manifest may be generated, at the time of the first manifest request, to include additional content, such as the targeted non-programing content and the customized programming content. Examples of the targeted non-programing content may include, but are not limited to, advertisements, personalized (per-user) advertisements, video advertisements, and graphical treatment (such as overlays). The targeted non-programing content may further include first interactive elements, such as an option to purchase goods or content, and second interactive elements. The second interactive elements may further affect the generation of the first disparate live media output stream manifest by providing various options. For example, a first option may be to skip a given ad, a second option may be to skip future ads for remainder of the playback of the first disparate live media output stream, a third option may be to choose one or more ads of a given category, or a fourth option may be too watch all ads immediately to avoid ads for the remainder of the playback. Examples of the customized programing content may include, but are not limited to, promotional content, short-form content, or alternate content (content replacing that of the requested first disparate live media output stream.

The DACIS 103 may further receive metadata associated with the content and additional content for the first disparate live media output stream from the CPDS 107. The metadata may include, for example, ad break locations, graphical treatment marker/triggers, SCTE35 markers, content duration, personalized content opportunities, and one or more decision point locations.

In accordance with an embodiment, the DACIS 103 may be configured to convert a pre-encoded media asset to the first disparate live media output stream to facilitate one or more subsequent modifications on the first disparate live media output stream. The one or more subsequent modifications may correspond to a user selection, a user preference, a change in a first programming schedule, or a time or geolocation-based rule. In accordance with an embodiment, the DACIS 103 may be configured to perform another conversion of remainder of the first disparate live media output stream into the one or more pre-encoded media assets to facilitate download of the one or more pre-encoded media assets at the consumer device and mitigate dependency on the DACIS 103 for playback of remaining portion.

In accordance with another aspect of the disclosure, upon receiving the first manifest request, a manifest of the first disparate live media output stream may be altered to include additional or alternate content, apart from the content originally scheduled for playback. The DACIS 103 may be configured to determine which content to include/replace by utilizing one or more parameters. The one or more parameters may include, but not limited to, URL requested for playback, and an identifier referencing a record for an existing first disparate live media output stream or an external connected system, such as the CPDS 107. The one or more parameters may include a plurality of client-specific parameters that may comprise user preferences and identifiers, consumer device preferences and identifiers, and one or more rules/rights governed by geolocation data and current position of playback of a first disparate live media output stream at the consumer device. The one or more parameters may include a plurality of client-specified attributes derived from user interaction with the consumer device. The plurality of client-specified attributes may include, for example, a preference for a given type and/or category (or categories) of programming content, a possible time constraint or duration to fill with content. The time constraint or duration to fill with content may be determined by user preferences from an external system, such as the repository of schedules, rights, and user preferences database 144, a range defined in the first client manifest request, schedule tolerances, as defined in the repository of schedules, rights, and user preferences database 144, device preferences/identifiers declared in the first manifest request, and a prior consumer request, or found in the repository of schedules, rights, and user preferences database 144. The time constraint or duration to fill with content may be further determined by geolocation information declared in the first manifest request or found in the first manifest request, or external database, such as the repository of schedules, rights, and user preferences database 144, or external systems, such as a content recommendation engine. The one or more parameters may further include rules, rights, and schedule data stored in the DACIS 103 or an adjacent, external system—such as the repository of schedules, rights, and user preferences database 144.

In accordance with an embodiment, the DACIS 103 may determine where to place new or alternate content within the requested disparate live media output stream. The DACIS 103 may utilize metadata, such as ad break locations, graphical treatment markers/triggers, SCTE35 markers, content duration, and one or more decision point locations. The metadata may be sourced from a system that has indexed metadata for the asset, such as the CPDS 107. The DACIS 103 may generate a new schedule from the determined alterations in the first disparate live media output stream. The DACIS 103 may transmit resulting schedule to the stream publishing engine 114 to generate a final disparate live media output stream. The final disparate live media output stream may be delivered back to originating client. The stream publishing engine 114 may generate the first disparate live media output stream manifest based on one of a pre-defined conversion modes. The pre-defined conversion modes may correspond to pre-encoded media assets to live stream mode, pre-encoded media assets to live stream mode with scalable architecture, a live stream to live stream mode, and a mixed mode corresponding to switching between pre-encoded media assets and live streams.

The final disparate live media output stream may contain one or more decision points, which, if configured, may be presented by the consumer device to the user. In this regard, the final disparate live media output stream may be delivered as a live stream between the decision points whether or not the programming content selected by a user is pre-encoded media asset or a live input stream. At the one or more decision points, the user interaction may correspond to one of a desired selection corresponding to the user interaction with one or more interactive elements, or a default selection corresponding to non-interaction of a user with the customized first programming content and/or the targeted first non-programming content in the first disparate live media output stream played back by the media player. The desired selection or the default selection may be transmitted to an external storage system that is the repository of schedules, rights, and user preferences database 144.

In accordance with an embodiment, at the one or more decision points, the one or more interactive elements may facilitate exclusion of the targeted first non-programming content or the customized first programming content and replacement by default content. The one or more interactive elements may further facilitate selection of alternate customized first programming content, selection of a subsequent second programming content, approval or disapproval of the selected customized first programming content, and/or exclusion of subsequent second non-programming content for a remaining portion of the first disparate live media output stream played back by the media player. The one or more interactive elements may further facilitate selection of one or more targeted first non-programming content of a specific category, or viewing of some or all of the targeted first non-programming content immediately to avoid some or all of the targeted first non-programming content for the remaining portion of the first disparate live media output stream played back by the media player.

In accordance with another aspect of the disclosure, the DACIS 103, upon the first manifest request, may seamlessly transition the first additional content to an alternate additional content according to determination made by the stream selection service 142, based on one or more transition parameters. The one or more transition parameters may comprise one or more parameters from the first manifest request, current state of the first disparate live media output stream manifest determined based on accessibility, regular update, and suitable encoding, digital rights management, and compatibility with the first client device, rules provided by a stream owner operator, and user preferences defined in the repository of schedules, rights, and user preferences database 144.

The DACIS 103 may retrieve alternate metadata for the alternate additional content from the CPDS 107. The alternate metadata may indicate a location to seamlessly transition from the first additional content to the alternate additional content, and may include ad break locations, graphical treatment markers/triggers, SCTE35 markers/triggers, content duration, and/or one or more decision points. The DACIS 103 may be configured to determine placement of the alternate additional content within the first disparate live media output stream manifest based on the associated indexed metadata and the alternate metadata. The DACIS 103 may generate an alternate programming schedule for the first client device based on the alternate additional content and the alternate metadata. The DACIS 103 may transmit the generated alternate programming schedule to the stream publishing engine 114. The stream publishing engine 114 may generate a final disparate live output stream manifest for the consumer device.

In accordance with an embodiment, the DACIS 103 may revoke the first disparate live media output stream manifest published for the first consumer device based on an identifier primitive associated with the first disparate live media output stream of the first consumer device in an instance in which a media player of the first consumer device is determined to be a plagiarized media player with unauthorized access to content. In such embodiment, the first disparate live media output stream may include at least one unique identifier inserted by the DACIS 103.

In accordance with another aspect of the disclosure, a system is provided for managing a pre-encoded media asset for immediate playback. The SSAI system 109 may be configured to generate, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments. The SSAI system 109 may be further configured to communicate the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device via a content delivery system for an immediate playback of a pre-encoded media asset. The SSAI system 109 may be further configured to assign a unique SID to the first client device to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request. The SSAI system 109 may be further configured to generate a final pre-encoded media asset manifest upon a receipt of the subsequent manifest request from the first client device based on a defined criterion. The final pre-encoded media asset manifest may comprise remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters.

FIG. 1B is a block diagram that illustrates an exemplary DACIS for publishing an updated disparate live media output stream in mixed mode based on user selection, in accordance with an exemplary embodiment of the disclosure. Referring to FIG. 1B, the DACIS 103 comprises a first programming schedule 111, an alternate programming schedule 113, a stream publishing engine 114, a personalized experience manager (PEM) 115, and an indexing and storage system 116. FIG. 1B further illustrates a content delivery system 130, which is an example of the network 108, client devices 132 a, . . . , 132 n, which correspond to the plurality of consumer devices 110 a, . . . , 110 n. There is further shown a per-client disparate live media output stream 117 a, . . . , 117 n for corresponding client device from the client devices 132 a, . . . , 132 n.

In some embodiments of the disclosure, the stream publishing engine 114, the PEM 115, and the indexing and storage system 116 may be integrated to form an integrated system, as illustrated in FIG. 1B. In some embodiments of the disclosure, as shown, the stream publishing engine 114, the PEM 115, and the indexing and storage system 116 may be distinct. In this regard, the PEM 115 may be implemented external to the DACIS 103 without loss of generality. Other separation and/or combination of the various entities of the exemplary media packaging and distribution system 102 illustrated in FIG. 1B may be done without departing from the spirit and scope of the various embodiments of the disclosure. In an embodiment, the implementation of the DACIS 103 may be on the server-side. In another embodiment, the implementation of the DACIS 103 may be on the client-side.

The first programming schedule 111 may correspond to an instruction set for a disparate live media output stream for a corresponding client device. The first programming schedule 111 may inform the stream publishing engine 114 about pre-encoded media assets and live input streams as well as when and how to switch between the various pre-encoded media assets and live input streams. The first programming schedule 111 may also support defining break durations for mid roll ads, break locations, and durations in the pre-encoded media asset and live input stream switches.

The alternate programming schedule 113 may correspond to an instruction set for an updated or alternate disparate live media output stream. The alternate programming schedule 113 may inform the stream publishing engine 114 about the alternate pre-encoded media asset and/or the alternate live input stream, and alternate additional content. Specifically, the alternate programming schedule 113 may indicate that when and how to switch between the various disparate live media output streams.

The stream publishing engine 114 in the DACIS 103 may be configured to generate disparate live media output stream manifests and variants of disparate live media output stream manifests. The stream publishing engine 114 may be configured to publish unique-to-client streaming manifests leveraging different indexes created by the indexing and storage system 116 from the various live input streams, pre-encoded media assets, targeted non-programming content and customized programming content based on a defined per-client schedule.

The PEM 115 in the DACIS 103 may be configured to personalize viewer experience of users by communicating with existing content decisioning systems, such as CDS 105, and executing/converting schedules provided, for example from the first programming schedule 111 to the alternate programming schedule 113. The PEM 115 in the DACIS 103 may be further configured to communicate with an ad server, such as the Ad decisioning server 106 a, and stitching in targeted first non-programming content and customized first programming content, as required by the first programming schedule 111 and user preferences. The PEM 115 in the DACIS 103 may be further configured to generate a schedule for a disparate live media output stream of personalized content (i.e., clips or movies), communicating with the stream selection service 142 to switch or failover to different disparate live media input streams, and control overlays and other events triggered via the disparate live media output stream. In accordance with an embodiment, the stream selection service 142 may be used to switch between different output streams when a client device is requesting directly from the stream selection service 142. In accordance with other embodiment, the stream selection service 142 may be used to switch between different streams that may act as inputs for the PEM 115 and/or stream publishing engine 114 to generate a new output stream.

The indexing and storage system 116 in the DACIS 103 may be configured to ingest pre-encoded media assets, advertisement, and (continuously) live stream source manifests, indexes the media content segments, indexes one or more program indicators (such as program boundaries), non-programming indicators (such as ad break locations, overlay opportunities credits, and DRM systems supported, in the repository of schedules, rights, and user preferences database 144.

The per-client disparate live media output streams 117 a, . . . , 117 n may correspond to disparate live media output stream comprising live input streams and/or pre-encoded media assets to be sent back to a client device, upon request, that has been generated from a per-client schedule, such as the first programming schedule 111. Various media container formats of the live input streams and/or pre-encoded media assets may include, but are not limited to, transport stream (TS), fragmented MP4 (fMP4), Common Media Application Format (CMAF) and the like.

The content delivery system 130 may correspond to the network 108, described in FIG. 1. The content delivery system 130 may comprise networks configured for distributing media content to the plurality of client devices 132 a, . . . , 132 n. Generally, the term “content,” “metadata,” “media,” and similar words are used interchangeably to refer to any type of media—audio, videos, datacasts, music, text, images, graphics, articles, still photos, animated photos, moving photos, photo galleries, video galleries, infographics, maps, polls, guest biographies, tweets or other social media, blog posts, and/or the like. The content delivery system 130 may be configured to provide a plurality of disparate live media output streams to the plurality of client devices 132 a, . . . , 132 n (in case packaged content is available on the network 108) or from the content packaging and distribution system 107 (in case packaged content is not available on the network 108). The plurality of disparate live media output streams may be provided to the plurality of client devices 132 a, . . . , 132 n via, for example, a transport stream, a segmented streaming, a progressive download, or any other modes of distributing a multimedia presentation, such as via an over-the-air content delivery/distribution network, a linear content delivery/distribution network, a cable content delivery/distribution network, a satellite content delivery/distribution network, an Internet Protocol (IP) based content delivery/distribution network, and/or the like.

The client devices 132 a, . . . , 132 n may correspond to consumer devices 110 a, . . . , 110 n. In accordance with an embodiment, the client devices 132 a, . . . , 132 n may be content recognition (CR)-enabled devices, such as automatic content recognition enabled devices. The client devices 132 a, . . . , 132 n may be configured to communicate with the Ad decisioning server 106 a, via the content delivery system 130, or a separate communication network.

The stream selection service 142 may comprise suitable logic, circuitry, and interfaces that may be configured to provide a client device, for example, the client device 132 a, requesting to view a disparate live media output stream with a correct variant of disparate live media output stream, based on the geolocation and identification of the client device 132 a, along with data retrieved from the repository of schedules, rights, and user preferences database 144. The stream selection service 142 may further receive user preferences of a user associated with the client device 132 a, for example, to view the recommended/desired existing disparate live media output stream on the client device 132 a. The stream selection service 142 may further store the received preferences in the repository of schedules, rights, and user preferences database 144, and also communicate with the PEM 115. The stream selection service 142 acts as an interface between the PEM 115 of the media packaging and distribution system 102 and the plurality of client devices 132 a, . . . , 132 n.

The repository of schedules, rights, and user preferences database 144 may comprise suitable logic, circuitry, and interfaces that may be configured to execute code to store content rights, user preferences, regional preferences, live schedules, and regional rights. For example, content rights may store availability and platform rights for live input streams in the first programming schedules, such as the first programming schedule 111, the user preferences may store preferences of individual user viewing preferences, the regional preferences may store regional viewing preferences, the live schedules may store the schedules for live input streams, and the regional rights may store regional blackout zones for the various sports leagues, for example. The repository of schedules, rights, and user preferences database 144 may further store data supplied from a stream owner/operator including requirements, preferences, such as pre-defined location-based viewing preferences, stream transition rules, and any required client data, such as service level and zip code.

In operation, in accordance with an aspect (regarding just-in-time insertion of non-programming content and/or programming content) of the disclosure, a media player in a consumer device, such as the consumer device 110 a, may send a first manifest request to the DACIS 103 to receive a disparate live media output stream manifest to begin or continue playback. The first manifest request may comprise one or more parameters, such as universal resource locators and/or identifiers referencing records for one or more live input streams or one or more pre-encoded media assets in the CPDS 107, a plurality of client-specific parameters, and a plurality of client-specified attributes derived from a user interaction with the consumer device, such as the consumer device 110 a. The plurality of client-specific parameters may comprise user preferences and identifiers, client device preferences and identifiers, and one or more rules governed by geolocation data and current position of playback of a first disparate live media output stream at the consumer device, such as the consumer device 110 a. The plurality of client-specified attributes may comprise the user interaction with interactive content in a customized first programming content and a targeted first non-programming content, and a preference for a type and/or category of the targeted first non-programming content and/or the customized first programming content. The user interaction with the interactive content may comprises a selection to exclude the targeted first non-programming content and/or the customized first programming content, a selection to include a subset of the targeted first non-programming content and/or the customized first programming content, and a selection to include all of the targeted first non-programming content and/or the customized first programming content within one or more specified non-programming content locations.

In case the first manifest request is for a first disparate live media output stream, the PEM 115 transmits the one or more parameters in the first manifest request to the stream selection service 142. The stream selection service 142 may determine live input streams and/or pre-encoded media assets, based on the one or more parameters in the first manifest request and in repository of schedules, rights, and user preferences database 144. The stream selection service 142 may transmit the determined identifiers or URLs of the live input streams and/or pre-encoded media assets to the PEM 115. The PEM 115 may then transmit the first manifest request to the CPDS 107 to retrieve metadata for the determined live input streams and/or pre-encoded media assets. The metadata may include, for example ad break locations, overlay markers/triggers, SCTE35 markers, and content duration.

The PEM 115 of the DACIS 103 may further transmit the received first manifest request to the CPDS 107 based on the selected one or more live input streams and/or one or more pre-encoded media assets. The PEM 115 may receive the indexed metadata, for example non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers and content duration, from the CPDS 107.

The PEM 115 may further identify the one or more content placement opportunities defined by the metadata associated with the one or more live input streams and/or one or more pre-encoded media assets. The PEM 115 may further receive additional content, such as targeted first non-programming content from the Ad decisioning server 106 a, and customized first programming content to match one or more personalization parameters from the CDS 105.

The PEM 115 may be configured to generate the first programming schedule 111 for a first client device, such as the client device 132 a, based on selected one or more live input streams and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content. The generated first programming schedule 111 may be delivered to the stream publishing engine 114. The stream publishing engine 114 may be configured to select the one or more live input stream manifests and/or the one or more pre-encoded media asset manifests published in the content delivery system 130. The indexing and storage system 116 may be configured to index the plurality of media segments indicated by the one or more pre-encoded media asset manifests and the one or more live input stream manifests, the associated indexed metadata, the targeted first non-programming content, and the customized first programming content may be indexed based on the first programming schedule 111 generated for the first client device, for example the client device 132 a. The stream publishing engine 114 may be further configured to publish the first disparate live media output stream manifest for the first client device, for example the client device 132 a. The DACIS 103 may transmit the published first disparate live media output stream manifest to the media player of the first client device for playback of the first disparate live media output stream, for example the disparate live media output stream 117 a.

In accordance with an embodiment, the PEM 115 may receive a user interaction from the media player of the first client device, for example the client device 132 a. The user interaction may correspond to one of a desired selection corresponding to the user interaction with one or more interactive elements, or a default selection corresponding to a non-interaction of the user with the customized first programming content and/or the targeted first non-programming content in the first disparate live media output stream 117 a played back by the media player. Based on the user interaction with the interactive content, the PEM 115 of the DACIS 103 may be configured to modify the remaining portion of the first programming schedule 111 that generates the first disparate live media output stream 117 a corresponding to the first manifest request generated by the first client device, such as the client device 132 a.

In accordance with another aspect (regarding personalized insertion of playlist of non-programming content and/or programming content) of the disclosure, the DACIS 103 may be configured to receive the first manifest request from the first client device, such as a client device 132 a, to begin or continue playback of a first disparate live media output stream, for example the disparate live media output stream 117 a. In such embodiment, in addition to the plurality of client-specific parameters described above, the plurality of client-specified attributes may comprise a preference for a given type and/or category (or categories) of targeted non-programming content or customized programming content, and a possible time constraint (duration) to fill with content. Thereafter, in similar manner as described above, the PEM 115 may transmit the one or more parameters in the first manifest request to the stream selection service 142. The stream selection service 142 may determine live input streams and/or pre-encoded media assets, based on the one or more parameters in the first manifest request and in repository of schedules, rights, and user preferences database 144. The stream selection service 142 may transmit the determined identifiers or URLs of the live input streams and/or pre-encoded media assets to the PEM 115. The PEM 115 may then transmit the first manifest request to the CPDS 107 to retrieve metadata for the determined live input streams and/or pre-encoded media assets. The metadata may include, for example, categories to which content is assigned to (for example, “basketball”, “sports”, “Knicks”), in addition to ad break locations, overlay markers/triggers, SCTE35 markers, and content duration.

The PEM 115 may identify one or more content placement opportunities defined by the metadata and may transmit a request to the CDS 105 to determine the customized first programming content from the CPDS 107 for matching one or more personalization parameters. Accordingly, the PEM 115 may generate the first programming schedule 111 defining locations and types of one or more decision points defined by the one or more content placement opportunities in the indexed metadata. The one or more decision points may define personalized content preferences, skipping of personalized content and moving to default content, and approval or disapproval of the personalized content. The remaining operations may be similar to the just-in-time insertion of non-programming content and/or programming content.

In accordance with another aspect (regarding stream failover) of the disclosure, the DACIS 103 may be configured to receive the first manifest request from the first client device, such as a client device 132 a. The first manifest request may comprise one or more parameters, as described above. The PEM 115 may transmit the received first manifest request that comprises the one or more parameters to the stream selection service 142. The stream selection service 142 may determine if the set of criteria associated with the first disparate live media output stream is satisfied. The set of criteria may include accessibility of the first disparate live media output stream, update of the first disparate live media output stream and/or compatibility of the first disparate live media output stream having media and/or a manifest with the first manifest request. The stream selection service 142 may be further configured to determine the one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters in the first manifest request, and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144. The stream selection service 142 may be further configured to determine the one or more live input streams and/or one or more pre-encoded media assets based on rules provided by a stream owner/operator (such as a regional blackout for the first client device leading to an alternative stream to watch) and user preferences (that exclude certain categories) defined in the repository of schedules, rights, and user preferences database 144.

When the set of criteria associated with the first disparate live media output stream is not satisfied, the stream selection service 142 may select a pre-encoded asset indicated in the first manifest request to continue playback as the first disparate live media output stream. The PEM 115 may receive the universal resource locators and/or identifiers that reference records for the selected one or more live input streams or alternate one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144. The PEM 115 may further transmit the received first manifest request to the CPDS 107 based on the selected one or more live input streams or alternate one or more pre-encoded media assets. The PEM 115 may further receive the alternate metadata for the alternate additional content from the CPDS 107. The metadata may include, for example, Ad break locations, overlay markers/triggers, SCTE35 markers/triggers, content duration, and one or more decision points. The alternate metadata may further include a location to transition from the first additional content to the alternate additional content. Thereafter, a placement of alternate additional content within the first disparate live media output stream manifest may be determined based on the associated indexed metadata and the alternate metadata. The PEM 15 may further generate the alternate programming schedule for the first client device, such as the client device 132 a, based on the alternate additional content and alternate metadata. Accordingly, the stream selection service 142 may publish the final disparate live output stream manifest for the first client device, such as the client device 132 a, based on the generated alternate programming schedule.

FIG. 1D is a block diagram that illustrates an exemplary system for managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure. Referring to FIG. 1D, the system 100D comprises the SSAI system 109 that further comprises an internal manifest index 109 a. The SSAI system 109 may be communicatively coupled to the CDS 105, the Ad decisioning servers 106 a, . . . , 106 n, the CPDS 107, the external data source 120, the content delivery system 130 (which is an example of the network 108), the client devices 132 a, . . . , 132 n, a memory 134, and the repository of schedules, rights, and user preferences database 144. The CPDS 107 may further comprise a content encoder/packager 107 a and a content metadata store 107 b.

Some of the components of the system 100D, such as the CDS 105, the Ad decisioning servers 106 a, . . . , 106 n, the CPDS 107, the SSAI system 109, the external data source 120, the content delivery system 130, the client devices 132 a, . . . , 132 n, and the repository of schedules, rights, and user preferences database 144 have already been described in detail in FIGS. 1A and 1B.

Multiple processors, such as the SSAI system 109 and the content encoder/packager 107 a, may comprise suitable logic, circuitry, interfaces, and/or code operable to process and execute a set of instructions stored in the memory 134. In some embodiments, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple processors, each providing portions of the necessary operations (for example, as a server cluster, a group of servers, or a multi-processor system), may be inter-connected and integrated. The processors may be implemented based on a number of processor technologies known in the art. Examples of the processors may be an ×86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processors.

The content encoder/packager 107 a may comprise suitable logic, circuitry, and interfaces that may be configured to execute code to determine a package that includes media content, such as pre-encoded media assets, and associated metadata. Thus, the content encoder/packager 107 a encodes and packages the media content into required on-demand formats for delivery to the client devices 132 a, . . . , 132 n. The media content may correspond to one or more of the programming content segments of the pre-encoded media assets transcoded to different types of streams for different types of devices, such as a TV or a mobile device, and marked with Nielson markers. Based on such a package, one or more encoded media assets may be dynamically generated for playout to one or more media players communicatively coupled through the content delivery system 130.

The content encoder/packager 107 a may be configured to publish the one or more encoded media assets, as one or more pre-encoded media assets, in real-time or near real-time to the content delivery system 130. The content encoder/packager 107 a may also be configured to provide near-real time redundancy. In accordance with an embodiment, the resulting converted output, i.e., one or more encoded media assets, that are generated by the content encoder/packager 107 a may be communicated to the indexing and storage system 116 which may be communicatively coupled with the plurality of consumer devices 108 a, . . . , 108 n. The content encoder/packager 107 a may also support a robust interface (for example, application data interface (ADI)) that defines the on-demand duration of the individual segments as well as encryption requirements and a service type to link for advertisement insertion.

The content metadata store 107 b may comprise suitable logic, circuitry, and interfaces that may be configured to store metadata associated with pre-encoded media assets. Examples of the metadata may include pre-encoded media asset identifiers, titles of the pre-encoded media asset, type of the pre-encoded media assets (such as movie series (season episode number)), genre, plot summary, duration, advertisement break locations, credit locations, scene descriptions, a short summary of the programming content segments, a short summary of ideal advertisement placements within the pre-encoded media asset manifests, a file format, digital right management (DRM), encryption information, length of the pre-encoded media assets, a date and/or time the pre-encoded media assets were added to a catalog of media content, a new item indicator for the pre-encoded media assets (for example, a new media asset that became available within the last 24 hours, last few days, last week, and/or the like), pre-encoded media asset classes, for example, a television show, a cartoon program, a movie, a news media, an episode, a game, a clip, a recorded sports event, interactive media, and/or the like. In accordance with an exemplary embodiment, the content metadata store 107 b may also store program-specific information (PSI) data as defined by ISO/IEC 13818-1 (MPEG-2), closed captioning data, and subtitles associated with the programming media segments. Other forms of metadata may be utilized without departing from the spirit and scope of the various embodiments of the disclosure.

In accordance with various embodiments, the metadata in the content metadata store 107 b may define a first set of content placement opportunities where non-scheduled programming content and/or non-programming content are inserted in a pre-encoded media asset manifest. The non-scheduled programming content may correspond to additional content provided by the CDS 105. Examples of the non-scheduled programming content may include media content that are not advertisements, such as gamebooks. The non-programming content may correspond to advertisement breaks or promotional content provided by an advertisement decision server, such as the Ad decisioning server 106 a. The first set of content placement opportunities may correspond to programming indicators associated with the non-scheduled programming content and non-programming indicators associated with the non-programming content.

The metadata may further define a second set of content placement opportunities where event-based programming content, such as opening credits, closing credits, timing, and previous episode recaps, occurs in the pre-encoded media asset manifest. The event-based programming content may correspond to an identifier corresponding to an event related to the content of the pre-encoded media asset. The second set of content placement opportunities may correspond to event markers.

In accordance with an embodiment, the metadata in the content metadata store 107 b may store timestamps of the first set of content placement opportunities and the second set of content placement opportunities upon the generation of the pre-encoded media asset.

The internal manifest index 109 a in the SSAI system 109 may comprise suitable logic, circuitry, and interfaces that may be configured to store programming segments of pre-encoded media asset manifests corresponding to the pre-encoded media assets. The internal manifest index 109 a may be a time-series database in which manifests are ingested. Such pre-encoded media asset manifests may be accessed from the internal manifest index 109 a by the SSAI system 109 based on the received initial manifest request.

The memory 134 may comprise suitable logic, circuitry, and/or interfaces that may be operable to store a machine code and/or a computer program with at least one code section executable by the processors, such as the SSAI system 109 and the content encoder/packager 107 a. The memory 134 may be configured to store information within the system 100D. In some embodiments, the memory 134 may include one or more volatile memory units. In other embodiments, the memory 134 may be a non-volatile memory unit or units. In yet other embodiments, the memory 134 may be another form of computer-readable medium, such as a magnetic or optical disk. Examples of forms of implementation of the memory 134 may include, but are not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Hard Disk Drive (HDD), and/or a Secure Digital (SD) card.

In operation, the content encoder/packager 107 a may generate a pre-encoded media asset comprising a plurality of programming content segments for distribution and adjust the plurality of programming content segments in the pre-encoded media asset based on the metadata retrieved from the content metadata store 107 b. The content encoder/packager 107 a may store the timestamps of the first set of content placement opportunities and the second set of content placement opportunities in the metadata upon the generation of the pre-encoded media asset. Also, the content encoder/packager 107 a may mark the start location and the end location of each of the first set of content placement opportunities and the second set of content placement opportunities in the pre-encoded media asset manifest. The content encoder/packager 107 a may store the pre-encoded media asset manifest in the content delivery system 130 or the internal manifest index 109 a.

In accordance with an embodiment, the SSAI system 109 may receive an initial manifest request from a first client device, such as the client device 132 a, to view a pre-encoded media asset. The SSAI system 109 may access the pre-encoded media asset manifest, based on received initial manifest request, from the content delivery system 130 or the internal manifest index 109 a. The SSAI system 109 may receive an instruction, based on the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules. In accordance with a first instruction, the SSAI system 109 may insert each non-scheduled programming content and/or non-programming content in the pre-encoded media asset manifest as an initial and final response to the initial manifest request for the playback of the pre-encoded media asset at the first client device, such as the client device 132 a in accordance with the first instruction based on the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules. In accordance with an embodiment, the initial pre-encoded media asset manifest may enable the immediate playback of the pre-encoded media asset at the first client device in accordance with a second instruction.

The SSAI system 109 may further determine the capability of the first client device, such as the client device 132 a, based on the targeting and/or non-targeting parameters, the external system and/or the set of pre-determined rules. The capability of the first client device may correspond to an extent of player integration with the SSAI system 109 and compatibility of the first client device with a required protocol. In accordance with an embodiment, the extent of the player integration with the system is limited and the first client device is incompatible with the required protocol. The SSAI system 109 may generate, based on the receipt of an initial manifest request from the first client device (such as the client device 132 a), the initial pre-encoded media asset manifest that comprises the initial set of programming content segments. The size of the initial set of programming content segments is verified to be equal to capacity of the playback buffer in the media player of the first client device. In accordance with another embodiment, the extent of the player integration with the system is complete and the first client device is compatible with the required protocol. The SSAI system 109 may generate, based on the receipt of the initial manifest request from the first client device (such as the client device 132 a), the initial pre-encoded media asset manifest. The initial pre-encoded media asset manifest may comprise the initial set of programming content segments up to the first content placement opportunity marked for insertion of the non-scheduled programming content and/or the non-programming content.

Accordingly, the SSAI system 109 may communicate the generated initial pre-encoded media asset manifest, as the first disparate live media output stream manifest, to the media player of the first client device (such as the client device 132 a) via the content delivery system 130 for an immediate playback of the pre-encoded media asset. In accordance with another embodiment, the initial pre-encoded media asset manifest may be independent of the non-scheduled programming content and/or the non-programming content. The initial pre-encoded media asset manifest may be based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules. The initial pre-encoded media asset manifest may enable the immediate playback of the pre-encoded media asset at the first client device in accordance with the second instruction.

The SSAI system 109 may further designate the initial pre-encoded media asset manifest to inform the media player of the first client device (such as the client device 132 a) to generate the subsequent manifest request as if it were a live or an event stream. Further, a unique SID may be assigned to the first client device (such as the client device 132 a) to record a session of the first client device for the subsequent manifest request or the final manifest request associated with the initial manifest request.

In accordance with an embodiment, the SSAI system 109 may verify the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content from corresponding servers. Further, the SSAI system 109 may determine whether the insertion of each of the non-scheduled programming content and/or the non-programming content is complete or incomplete in the updated pre-encoded media asset manifest based on the received information.

In accordance with an embodiment, the SSAI system 109 may generate the final pre-encoded media asset manifest upon the receipt of the subsequent manifest request from the first client device, such as the client device 132 a, based on the defined criterion. The defined criterion may correspond to the determination that the insertion of the non-scheduled programming content and/or the non-programming content in the final pre-encoded media asset manifest is complete. The SSAI system 109 may communicate the final pre-encoded media asset manifest to the first client device, such as the client device 132 a, in response to the subsequent manifest request when the defined criterion is met. The final pre-encoded media asset manifest may be designated to inform the media player of the first client device, such as the client device 132 a, to cease further generation of the subsequent manifest request. At this instant, the SSAI system 109 may store the initial, the updated, and/or the final pre-encoded media asset manifests as a set of asset manifests corresponding to the unique SID for the designated period of time.

The SSAI system 109 may further determine whether the pre-encoded media asset manifest and/or the metadata include the second set of content placement opportunities. In accordance with an embodiment, the SSAI system 109 may add the additional content segments corresponding to the pre-encoded media asset, the non-scheduled programming content segments and/or the non-programming content segments in the updated pre-encoded media asset manifest to provide additional time duration. The SSAI system 109 may complete the insertion of the non-scheduled programming content and/or the non-programming content in the updated pre-encoded media asset manifest at a portion of or an entire first set of content placement opportunities defined in the metadata.

In accordance with another embodiment, the SSAI system 109 may add the plurality of event-based programming content segments and the additional content segments in the updated pre-encoded media asset manifest when the pre-encoded media asset manifest and/or the metadata includes the second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest. The size of the additional content segments matches with capacity of a playback buffer in the media player of the first client device, such as the client device 132 a. The SSAI system 109 may allow the media player of the first client device, such as the client device 132 a, to begin the immediate playback after the marked end location of the plurality of event-based programming content segments upon a receipt of an input from the first client device, such as the client device 132 a, to skip the event-based programming content.

In accordance with an embodiment, the SSAI system 109 may communicate an updated pre-encoded media asset manifest to the first client device, such as the client device 132 a, in response to the updated manifest request. The SSAI system 109 may designate the updated pre-encoded media asset manifest to inform the media player of the first client device, such as the client device 132 a, to generate the subsequent manifest request or the final manifest request. Such cycle is repeated until the final pre-encoded media asset manifest with the non-scheduled programming content and/or the non-programming content can be generated that meets the defined criterion. Once generated, the final pre-encoded media asset manifest may be communicated to the first client device, such as the client device 132 a. As described above, the final pre-encoded media asset manifest may be designated to inform the media player of the first client device, such as the client device 132 a, to cease further generation of the subsequent manifest request. At this instant, the SSAI system 109 may store the initial, the updated, and/or the final pre-encoded media asset manifests as a set of asset manifests corresponding to the unique SID for the designated period of time.

FIG. 2 illustrates segmentation of live input streams and pre-encoded media assets for the first programming schedule 111 or the alternate programming schedule 113 for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content by the DACIS 103 of FIG. 1B, in accordance with an exemplary embodiment of the disclosure. Referring to the exemplary arrangement of FIG. 2, there is shown a first live input stream 202, a first pre-encoded media asset 204, and a second live input stream 206. There is also shown a targeted first non-programming content 208 placed after the first live input stream 202, and a customized first programming content 210 placed after the first pre-encoded media asset 204. The first live input stream 202 may be segmented into a first set of video segments 202 a, 202 b, 202 c, . . . , 202 n. Similarly, the first pre-encoded media asset 204 and the second live input stream 206 may also be segmented into second set of video segments 204 a, 204 b, 204 c, . . . , 204 n, and third set of video segments 206 a, 206 b, 206 c, . . . , 206 n respectively. By way of example, the segmentation may be executed by a segmenting system (for example a live stream encoder/packager and/or a content encoder/packager (not shown)) during a preparation stage of the media assets. The encode stage may create various quality levels and the package stage segments the content into the short segments, and produces the correct format, such as TS, fMP4, or CMAF and encrypts the media content to prevent piracy. In accordance with an embodiment, the segments of the first set of video segments 202 a, 202 b, 202 c, . . . , 202 n, the second set of video segments 204 a, 204 b, 204 c, . . . , 204 n, and third set of video segments 206 a, 206 b, 206 c, . . . , 206 n, may be segmented into consistent length, for example, 10 seconds segments. It may be advantageous to have a consistent and smaller file size of segments to be able to quickly push to the content delivery system 130, and also for quick downloading by a media player at the end-user side, such as on the plurality of consumer devices 110 a, . . . , 110 n.

It should be understood by those skilled in the art that various changes may be made and segments of different file sizes (or length) may be used without departure from the scope of the present disclosure. Further, other streaming protocols may require a different processing of media content. Thus, the scope of the disclosure should not be limited to the processing or preparation of media content to allow delivery using different delivery methods, streaming protocols, or distribution system, known in the art. Further, instead of the live input streams and pre-encoded media asset arranged, as shown, different arrangements per the first programming schedule 111 or the alternate programming schedule 113 may be possible with respect to interstitial content items, such as the targeted first non-programming content 208 and the customized first programming content 210.

The insertion of the live input stream manifests, pre-encoded media asset manifests, the targeted first non-programming content 208 and the customized first programming content 210 may be done on-the-fly based on dynamic scheduling by the PEM 115 that generates the first programming schedule 111 or the alternate programming schedule 113. The insertion may be driven by real time or near-real time content context analysis, user-selection on the consumer devices 110 a, . . . , 110 n, or driven by external data received from the external data source 120. The PEM 115 in association with the stream selection service 142 may be configured to insert live input streams, such as the first live input stream 202 and the second live input stream 206, or pre-stored media assets, such as the first pre-encoded media asset 204, the targeted first non-programming content 208 and the customized first programming content 210, in an existing disparate live media output stream based on manipulation of a manifest the existing disparate live media output stream, such as an existing channel.

In accordance with an embodiment, each segment of the first set of video segments 202 a, 202 b, 202 c, . . . , 202 n, the second set of video segments 204 a, 204 b, 204 c, . . . , 204 n, and third set of video segments 206 a, 206 b, 206 c, . . . , 206 n, may be further processed to be stored at various quality levels, and content encryption modes for the purposes of adaptive bitrate streaming and digital rights management, for example, the video segment 202 a may be stored in a plurality of quality levels, for example, high definition (HD), high dynamic range (HDR) video, or different quality levels in accordance with specified pixel resolutions, bitrates, frame rates, and/or sample frequencies. As each of the media content, such as 202 to 206, are encoded, segmented, and stored with the plurality of quality levels in a media content master storage system. The media content may be re-used to create new channels, such as a new disparate live media output stream, without having to re-encode a selected live input stream or a pre-encoded media asset when a new disparate live media output stream is created using the live input streams or a pre-encoded media asset.

For the sake of brevity, and with reference to FIG. 2, there is shown an example of publishing the first or the updated (or alternate) disparate live media output streams based on dynamic insertion of targeted non-programming content and customized programming content by the DACIS 103 of FIG. 1B. It is to be understood that media packaging for different delivery methods (such as analog terrestrial broadcast, digital terrestrial broadcast, direct-to-home satellite broadcast, cable, other Internet Protocol (IP)-based delivery methods, over-the-top television (OTT)), different streaming protocols, or distribution system, may be different. The media content may be prepared to be viewed one or more of the plurality of consumer devices 110 a, . . . , 110 n, based on at least the desired delivery method, delivery conditions, content protection requirements, to satisfy operational and technical requirements, as needed. The operational and technical requirements may include, but are not limited to, media encoding, media segmentation, programming schedule (or manifest) creation or manipulation requirements, desired media encryption, and/or metadata signaling requirements. For example, in certain scenarios and for certain media content delivery methods, network bandwidth, network conditions, or device-type where media content is to be consumed may not be variable or known in advance. In such a case, creating different quality levels for same media content may not be required. Further, based on different operational and technical requirements, publishing of disparate live media output stream may be different. The media content that is prepared and distributed may include both the programming content, such as long-form presentations, short-form presentations, news or sporting events; and non-programming content, such as paid advertisements, public service advertisements, or promotional material.

FIG. 3 illustrates an exemplary scenario associated with publishing a disparate live media output stream by the DACIS 103 of FIG. 1B, in accordance with an exemplary embodiment of the disclosure. Referring to the exemplary scenario 300, there are illustrated two disparate live media output streams 302 and 304 published for two users associated with the client devices 132 a and 132 n, respectively. The disparate live media output stream 302 may be existing disparate live media output stream for the client device 132 a. The disparate live media output stream 304 may be a disparate per-client live media output stream published based on dynamic insertion of targeted non-programming content and customized programming content by the DACIS 103 of FIG. 1B for the client device 132 n.

The live NBA game may be scheduled to start at 8:00 pm. However, a user associated with the client device 132 n tunes in early to watch the NBA game, for example at 7:15 pm. However, the user may not be interested in watching the end of the current programming media content. In such a case, the PEM 115 in the DACIS 103 may determine targeted non-programming content, such as sports items ads, and customized programming content, such as NBA highlights of previous game and generates the alternate programming schedule 113. Accordingly, the stream publishing engine 114 in the DACIS 103 may publish an alternate disparate live media output stream 117 n for the client device 132 n. At 8:00 pm, the DACIS 103 may switch back to the live NBA game scheduled at 8:00 pm.

FIGS. 4A to 4D depict flowcharts illustrating exemplary operations for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content in the media packaging and distribution system 102 of FIG. 1B, in accordance with an exemplary embodiment of the disclosure. Specifically, flowcharts 400A and 400B collectively depicts a method for just-in-time insertion of non-programming content and/or programming content, in accordance with an embodiment of the disclosure. Flowchart 400C depicts a method for personalized insertion of non-programming content and/or programming content, in accordance with an embodiment of the disclosure. Flowchart 400E depicts a method for stream failover, in accordance with an embodiment of the disclosure.

Referring to FIGS. 4A and 4B, flowcharts 400A and 400B collectively depicts a method for just-in-time insertion of non-programming content and/or programming content, in accordance with an embodiment of the disclosure.

At 402A, a first manifest request may be received from a first client device. In accordance with an embodiment, the DACIS 103 may be configured to receive the first manifest request from the first client device, such as a client device 132 a, to begin or continue playback of a first disparate live media output stream, for example the disparate live media output stream 117 a. The first manifest request may comprise one or more parameters. Examples of the one or more parameters may include, but are not limited to, universal resource locators and/or identifiers referencing records for existing one or more live input streams or one or more pre-encoded media assets in the CPDS 107, a plurality of client-specific parameters, and a plurality of client-specified attributes derived from a user interaction with the first client device, such as the client device 132 a. Examples of the plurality of client-specific parameters may include, but are not limited to, user preferences and identifiers, client device preferences and identifiers, and one or more rules governed by geolocation data and current position of playback of a first disparate live media output stream, such as the disparate live media output stream 117 a, at the first client device, such as the client device 132 a. In an embodiment, the client-specified attributes derived from a user interaction with the first client device may include, but are not limited to, the user interaction with interactive content in a customized first programming content and a targeted first non-programming content, and a preference for a type and/or category of the targeted first non-programming content and/or the customized first programming content. The user interaction with the interactive content may comprise, for example, a selection to exclude the targeted first non-programming content and/or the customized first programming content, a selection to include a subset of the targeted first non-programming content and/or the customized first programming content, and a selection to include all of the targeted first non-programming content and/or the customized first programming content within one or more specified non-programming content locations.

At 404A, the received first manifest request that comprises one or more parameters may be transmitted to the stream selection service 142. In an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the received first manifest request that comprises the one or more parameters to the stream selection service 142.

In an embodiment, based on the received first manifest request, the stream selection service 142 may be configured to select one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144. Accordingly, the stream selection service 142 may be configured to return universal resource locators and/or identifiers that reference records for the selected one or more live input streams and/or one or more pre-encoded media assets to the PEM 115.

At 406A, the universal resource locators and/or identifiers that reference records for the selected one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144 may be received. In an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the universal resource locators and/or identifiers that reference records for the selected one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144.

At 408A, the received first manifest request may be transmitted to the CPDS 107 based on the selected one or more live input streams and/or one or more pre-encoded media assets. In an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the received first manifest request to the CPDS 107 based on the selected one or more live input streams and/or one or more pre-encoded media assets.

In an embodiment, based on the received first manifest request, the CPDS 107 may be configured to retrieve indexed metadata, for example, non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers and content duration. Accordingly, the CPDS 107 may be configured to return the indexed metadata to the PEM 115.

At 410A, the indexed metadata may be received from the CPDS 107. In an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the indexed metadata from the CPDS 107. Examples of the indexed metadata may include, but are not limited to, non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers and content duration, as described above.

At 412A, one or more content placement opportunities defined by the metadata associated with the one or more live input streams and/or one or more pre-encoded media assets may be identified. In an embodiment, the PEM 115 of the DACIS 103 may be configured to identify the one or more content placement opportunities defined by the metadata associated with the one or more live input streams and/or one or more pre-encoded media assets. Examples of the one or more content placement opportunities may include, but are not limited to, non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers and personalized content opportunity. In an embodiment, for the identified one or more content placement opportunities, the PEM 115 of the DACIS 103 may be configured to determine additional content, such as non-programming content (such as advertisements), personalized programming content (such as promotional content), graphical treatment (such as overlays), and one or more decision point locations.

At 414, a request may be transmitted to the Ad decisioning server 106 a to determine targeted first non-programming content. In an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the request to the Ad decisioning server 106 a to determine the targeted first non-programming content.

In an embodiment, based on the request, the Ad decisioning server 106 a may be configured to identify the targeted first non-programming content, such as an advertising or an graphical treatment content, to be scheduled in one or more content placement opportunities, based on the one or more parameters. In an embodiment, the Ad decisioning server 106 a may be configured to identify the targeted first non-programming content based on execution of a non-programming content service based on rules and conditions defined in additional parameters of the repository of schedules, rights, and user preferences database 144, and the one or more parameters defined in the first manifest request. Accordingly, the Ad decisioning server 106 a may be configured to transmit the identified targeted first non-programming content to the PEM 115 of the DACIS 103.

At 416, the targeted first non-programming content may be received from the Ad decisioning server 106 a. In an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the targeted first non-programming content from the Ad decisioning server 106 a.

At 418, a request may be transmitted to the CDS 105 to determine a customized first programming content to match one or more personalization parameters. In an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the request to the CDS 105. The CDS 105 may determine a customized first programming content to match one or more personalization parameters.

In an embodiment, based on the request, the CDS 105 may be configured to identify the customized first programming content based on the one or more parameters in the first manifest request, and the rules and conditions defined in the additional parameters of the repository of schedules, rights, and user preferences database 144. Accordingly, the CDS 105 may be configured to transmit the identified customized first programming content to the PEM 115 of the DACIS 103.

At 420, the customized first programming content may be received from the CDS 105. In an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the customized first programming content from the CDS 105.

At 422, a first additional content comprising the customized first programming content and the targeted first non-programming content may be determined for the first client device based on the one or more parameters and the associated indexed metadata. In an embodiment, the PEM 115 of the DACIS 103 may be configured to determine the first additional content comprising the customized first programming content, received from the CDS 105, and the targeted first non-programming content, received from the Ad decisioning server 106 a. The first additional content may be determined for the first client device, such as the client device 132 a, based on the one or more parameters and the associated indexed metadata, received from the CPDS 107.

At 424, a first programming schedule 111 may be generated for the first client device based on the selected one or more live input streams and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content. In an embodiment, the PEM 115 of the DACIS 103 may be configured to generate the first programming schedule 111 for the first client device, such as the client device 132 a, based on selected one or more live input streams and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content.

In accordance with an embodiment, the generated first programming schedule 111 may not include the first additional content, in accordance with the one or more parameters in the first manifest request. In accordance with another embodiment, the generated first programming schedule 111 may include the first additional content, in accordance with the one or more parameters in the first manifest request. In accordance with another embodiment, the generated first programming schedule 111 may include a subset of the first additional content, in accordance with the one or more parameters in the first manifest request.

In accordance with an embodiment, the first additional content scheduled to be inserted, may be inserted into, for example, one or more pre-encoded assets in accordance with appropriate markers. The appropriate markers may be defined in the metadata of the one or more pre-encoded assets, and rules and conditions defined in the repository of schedule, rights, and user preferences database 144.

In accordance with an embodiment, the generated first programming schedule 111 may define locations and types of one or more decision points defined by the one or more content placement opportunities in the indexed metadata. The one or more decision points may be included in the first programming schedule 111. Within the first programming schedule 111, the one or more decision points may define various types of the decision points, for example, an Ad preference, skip next ad, skip future ads, watch ads immediately instead of at future ad locations, or personalized content preferences.

In an exemplary embodiment, the one or more pre-encoded media assets are scheduled and the one or more decision points, defined by the one or more content placement opportunities, are inserted in the first programming schedule 111. In such exemplary embodiment, the first programming schedule 111 may be configured to control the one or more pre-encoded media asset manifests to be published as, for example, the first disparate live media output stream manifest. Further, the first programming schedule 111 may include, for example, segments, markers, the one or more content placement opportunities, up to and including next available decision point.

At 426, the first programming schedule 111 may be delivered to the stream publishing engine 114. In accordance with an embodiment, the PEM 115 in the DACIS 103 may be configured to deliver the first programming schedule 111 to the stream publishing engine 114.

At 428, one or more live input stream manifests and/or one or more pre-encoded media asset manifests published in the content delivery system 130 may be selected. In accordance with an embodiment, the stream publishing engine 114 in the DACIS 103 may be configured to select the one or more live input stream manifests and/or the one or more pre-encoded media asset manifests published in the content delivery system 130.

At 430, a plurality of media segments indicated by the one or more pre-encoded media asset manifests and the one or more live input stream manifests, the associated indexed metadata, the targeted first non-programming content, and the customized first programming content may be indexed based on the first programming schedule 111 generated for the first client device. In accordance with an embodiment, the indexing and storage system 116 may be configured to index the plurality of media segments indicated by the one or more pre-encoded media asset manifests and the one or more live input stream manifests, the associated indexed metadata, the targeted first non-programming content, and the customized first programming content may be indexed based on the first programming schedule 111 generated for the first client device, for example the client device 132 a.

At 432, a first disparate live media output stream manifest for the first client device may be published based on insertion of the selected one or more live input stream manifests and/or the one or more pre-encoded media asset manifests, the associated indexed metadata, and the determined first additional content, into the first disparate live media output stream manifest, in accordance with the first programming schedule 111 generated for the first client device. In accordance with an embodiment, the stream publishing engine 114 in the DACIS 103 may be configured to publish the first disparate live media output stream manifest for the first client device, for example the client device 132 a. The publication may be based on insertion of the selected one or more live input stream manifests and/or the one or more pre-encoded media asset manifests, the associated indexed metadata, and the determined first additional content, into the first disparate live media output stream manifest, in accordance with the first programming schedule 111 generated for the first client device, for example the client device 132 a.

At 434, the published first disparate live media output stream manifest may be transmitted to a media player of the first client device for playback of the first disparate live media output stream, for example the disparate live media output stream 117 a. In accordance with an embodiment, the DACIS 103 may be configured to transmit the published first disparate live media output stream manifest to the media player of the first client device for playback of the first disparate live media output stream, for example the disparate live media output stream 117 a. In accordance with an embodiment, the first disparate live media output stream manifest for the first client device, for example the client device 132 a, may be generated based on one of a pre-defined conversion modes. The pre-defined conversion modes may correspond to conversion of pre-encoded media assets to live stream mode, pre-encoded media assets to live stream mode with scalable architecture, a live stream to live stream mode, and a mixed mode corresponding to switches between pre-encoded media assets and live streams.

In accordance with an embodiment, the published first disparate live media output stream manifest may be delivered to the first client device, for example the client device 132 a. Accordingly, the media player of the first client device, for example the client device 132 a, may begin or continue playback of the first disparate live media output stream 117 a. Further, the media player, during playback of the first disparate live media output stream 117 a at the first client device, for example the client device 132 a, presents one or more decision points defined by the interactive content to initiate a user interaction at the first client device, for example the client device 132 a.

In accordance with an embodiment, during the playback, in case a decision point exists, is enabled, and presented by the first client device, for example the client device 132 a, the user of the client device 132 a may interact with one or more interactive elements at the decision point and influence (or modify) remaining first disparate live media output stream 117 a.

For example, in an embodiment of just-in-time non-programming content insertion, at the one or more decision points, the user interaction corresponds to one of a desired selection corresponding to the user interaction with one or more interactive elements, or a default selection corresponding to non-interaction of a user with the customized first programming content and/or the targeted first non-programming content in the first disparate live media output stream 117 a played back by the media player. In another example, in an embodiment of personalized content playlist, at the one or more decision points, the user interaction corresponds to one of exclusion of the targeted first non-programming content or the customized first programming content and replacement by default content, selection of alternate customized first programming content, selection of a subsequent second programming content, approval or disapproval of the selected customized first programming content, exclusion of subsequent second non-programming content for a remaining portion of the first disparate live media output stream 117 a played back by the media player, selection of one or more targeted first non-programming content of a specific category, or viewing of some or all of the targeted first non-programming content immediately to avoid some or all of the targeted first non-programming content for the remaining portion of the first disparate live media output stream played back by the media player.

At 436, the user interaction may be received that corresponds to one of a desired selection corresponding to the user interaction with one or more interactive elements, or a default selection corresponding to a non-interaction of the user with the customized first programming content and/or the targeted first non-programming content in the first disparate live media output stream 117 a played back by the media player. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the user interaction may be received. The user interaction may correspond to one of a desired selection corresponding to the user interaction with one or more interactive elements, or a default selection corresponding to a non-interaction of the user with the customized first programming content and/or the targeted first non-programming content in the first disparate live media output stream 117 a played back by the media player.

At 438, a remaining portion of the first programming schedule 111 that generates the first disparate live media output stream 117 a corresponding to the first manifest request generated by the first client device, such as the client device 132 a, may be modified based on the user interaction with the interactive content. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to modify the remaining portion of the first programming schedule 111 that generates the first disparate live media output stream 117 a corresponding to the first manifest request generated by the first client device, such as the client device 132 a, based on the user interaction with the interactive content.

At 440, a desired selection or the default selection may be transmitted to an external storage system that is the repository of schedules, rights, and user preferences database 144. In accordance with an embodiment, the first client device, for example the client device 132 a, may be configured to transmit the desired selection or the default selection to the external storage system that is the repository of schedules, rights, and user preferences database 144.

In accordance with an embodiment, the user interaction or non-interaction result may be sent to future client manifest requests to influence the remainder of the first disparate live media output stream 117 a. This may allow for a user choice, such as to skip an ad, to result with another manifest request to the DACIS 103 to update the existing first disparate live media output stream 117 a with the intended behavior and affect playback of the first disparate live media output stream 117 a within the first client device.

Referring to FIG. 4C, flowchart 400C depicts a method for personalized insertion of playlist of non-programming content and/or programming content, in accordance with an embodiment of the disclosure.

At 402B, a first manifest request may be received from a first client device. In accordance with an embodiment, the DACIS 103 may be configured to receive the first manifest request from the first client device, such as a client device 132 a, to begin or continue playback of a first disparate live media output stream, for example the disparate live media output stream 117 a. The first manifest request may comprise one or more parameters. Examples of the one or more parameters may include, but are not limited to, universal resource locators and/or identifiers referencing records for existing one or more live input streams or one or more pre-encoded media assets in the CPDS 107, a plurality of client-specific parameters, and a plurality of client-specified attributes derived from a user interaction with the first client device, such as the client device 132 a. Examples of the plurality of client-specific parameters may include, but are not limited to, user preferences and identifiers, client device preferences and identifiers, and one or more rules governed by geolocation data and current position of playback of a first disparate live media output stream, such as the disparate live media output stream 117 a, at the first client device, such as the client device 132 a. In another embodiment, the client-specified attributes derived from a user interaction with the first client device may include, but are not limited to, a preference for a type and/or category of the targeted first non-programming content and/or the customized first programming content, and a possible time constraint (or duration) to fill with the targeted first non-programming content and/or the customized first programming content. The user interaction with the interactive content may comprise, for example, a selection to exclude the targeted first non-programming content and/or the customized first programming content, a selection to include a subset of the targeted first non-programming content and/or the customized first programming content, and a selection to include all of the targeted first non-programming content and/or the customized first programming content within one or more specified non-programming content locations.

The user interaction with the interactive content may comprise, for example, a selection to exclude the targeted first non-programming content and/or the customized first programming content, a selection to include a subset of the targeted first non-programming content and/or the customized first programming content, and a selection to include all of the targeted first non-programming content and/or the customized first programming content within one or more specified non-programming content locations.

At 404B, the received first manifest request that comprises one or more parameters may be transmitted to the stream selection service 142. In an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the received first manifest request that comprises the one or more parameters to the stream selection service 142.

In an embodiment, based on the received first manifest request, the stream selection service 142 may be configured to select one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144. Accordingly, the stream selection service 142 may be configured to return universal resource locators and/or identifiers that reference records for the selected one or more live input streams and/or one or more pre-encoded media assets to the PEM 115.

At 406B, the universal resource locators and/or identifiers that reference records for the selected one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144 may be received. In an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the universal resource locators and/or identifiers that reference records for the selected one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144.

At 408B, the received first manifest request may be transmitted to the CPDS 107 based on the selected one or more live input streams and/or one or more pre-encoded media assets. In an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the received first manifest request to the CPDS 107 based on the selected one or more live input streams and/or one or more pre-encoded media assets.

In an embodiment, based on the received request, the CPDS 107 may be configured to retrieve indexed metadata, for example, non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers, content duration, and categories (such as, “basketball”, “sports”, “Knicks”) to which the programming content has been assigned.

At 410B, the indexed metadata may be received from the CPDS 107. In an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the indexed metadata from the CPDS 107. Examples of the indexed metadata may include, but are not limited to, non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers and content duration, as described above.

At 412B, one or more content placement opportunities defined by the metadata associated with the one or more live input streams and/or one or more pre-encoded media assets may be identified. In an embodiment, the PEM 115 of the DACIS 103 may be configured to identify the one or more content placement opportunities defined by the metadata associated with the one or more live input streams and/or one or more pre-encoded media assets. Examples of the one or more content placement opportunities may include, but are not limited to, non-programming indicators, such as ad break locations, graphical treatment indicators, such as overlay markers/triggers, programming indictors, such as SCTE35 markers and personalized content opportunity. In an embodiment, for the identified one or more content placement opportunities, the PEM 115 of the DACIS 103 may be configured to determine additional content, such as non-programming content (such as advertisements), personalized programming content (such as promotional content), graphical treatment (such as overlays), and one or more decision point locations.

At 442, a request may be transmitted to the CDS 105 to determine a customized first programming content from the CPDS 107 for matching one or more personalization parameters. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit a request to the CDS 105 to determine the customized first programming content from the CPDS 107 for matching one or more personalization parameters. Examples of the one or more personalization parameters may include, but are not limited to, user preferences and identifiers from the first manifest request or retrieved from the repository of schedules, rights, and user preferences database 144, and time constraints. The time constraints may be determined based on user preferences retrieved from the repository of schedules, rights, and user preferences database 144, a range defined in the first manifest request, and schedule tolerances defined in the repository of schedules, rights, and user preferences database 144, client device preferences or identifiers from the first manifest request or retrieved from the repository of schedules, rights, and user preferences database 144, geolocation information from the first manifest request or retrieved from the repository of schedules, rights, and user preferences database 144, and/or a content recommendation engine.

At 444, the first programming schedule 111 may be generated for the first client device based on the selected one or more live input streams and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to generate the first programming schedule 111 for the first client device, such as the client device 132 a, based on the selected one or more live input streams and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content.

In accordance with an embodiment, the first additional content scheduled to be inserted, may be inserted into, for example, one or more pre-encoded assets in accordance with appropriate markers. The appropriate markers may be defined in the metadata of the one or more pre-encoded assets, and rules and conditions defined in the repository of schedule, rights, and user preferences database 144.

In accordance with an embodiment, the generated first programming schedule 111 may define locations and types of one or more decision points defined by the one or more content placement opportunities in the indexed metadata. Such one or more decision points may be included in the first programming schedule 111. Within the first programming schedule 111, the one or more decision points may define personalized content preferences, skipping of personalized content and moving to default content, and approval or disapproval of the personalized content.

In an exemplary embodiment, the one or more pre-encoded media assets are scheduled and the one or more decision points, defined by the one or more content placement opportunities, are inserted in the first programming schedule 111. In such exemplary embodiment, the first programming schedule 111 may be configured to control the one or more pre-encoded media asset manifests to be published as, for example, the first disparate live media output stream manifest. Further, the first programming schedule 111 may include, for example, segments, markers, the one or more content placement opportunities, up to and including next available decision point. Thereafter, control passes to 426 in flowchart 400B and exemplary operations till 440 may be performed in similar manner as described above.

Referring to FIG. 4D, there is illustrated a flowchart 400D depicting a method for stream failover, in accordance with an embodiment of the disclosure.

At 402C, a first manifest request may be received from a first client device. In accordance with an embodiment, the DACIS 103 may be configured to receive the first manifest request from the first client device, such as a client device 132 a, to begin or continue playback of a first disparate live media output stream, for example the disparate live media output stream 117 a. The first manifest request may comprise one or more parameters. Examples of the one or more parameters may include, but are not limited to, universal resource locators of existing one or more live input streams, identifiers referencing records for existing one or more live input streams or one or more pre-encoded media assets in the CPDS 107, and a plurality of client-specific parameters. Examples of the plurality of client-specific parameters may include, but are not limited to, user preferences and identifiers, client device preferences and identifiers, and one or more rules governed by geolocation data and current position of playback of a first disparate live media output stream, such as the disparate live media output stream 117 a, at the first client device, such as the client device 132 a.

At 404C, received first manifest request that comprises one or more parameters may be transmitted to the stream selection service 142. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the received first manifest request that comprises the one or more parameters to the stream selection service 142.

At 454, it may be determined that a set of criteria associated with the first disparate live media output stream is satisfied. In accordance with an embodiment, the stream selection service 142 may be configured to determine if the set of criteria associated with the first disparate live media output stream is satisfied. The set of criteria may include an accessibility of the first disparate live media output stream, update of the first disparate live media output stream and/or compatibility of the first disparate live media output stream having media and/or a manifest with the first manifest request. The stream selection service 142 may be further configured to determine the one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters in the first manifest request, and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144. The stream selection service 142 may be further configured to determine the one or more live input streams and/or one or more pre-encoded media assets based on rules provided by a stream owner/operator (such as a regional blackout for the first client device leading to an alternative stream to watch) and user preferences (that exclude certain categories) defined in the repository of schedules, rights, and user preferences database 144.

In accordance with an embodiment, when the first disparate live media output stream is not accessible, the first disparate live media output stream is not updated and/or the first disparate live media output stream having media and/or manifest that is not compatible with the first manifest request. Further, in an absence of one or more live input streams, the stream selection service 142 may be configured to select a pre-encoded asset indicated in the first manifest request to continue playback as the first disparate live media output stream. In such embodiment, control passes to operation 456. Otherwise, control passes to operation 406A of the flowchart 400A.

At 456, universal resource locators and/or identifiers that reference records for the selected one or more live input streams or alternate one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144 may be received. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the universal resource locators and/or identifiers that reference records for the selected one or more live input streams or alternate one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144.

At 458, a received first manifest request may be transmitted to the CPDS 107 based on the selected one or more live input streams or alternate one or more pre-encoded media assets. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to transmit the received first manifest request to the CPDS 107 based on the selected one or more live input streams or alternate one or more pre-encoded media assets.

At 460, alternate metadata for alternate additional content may be received from the CPDS 107. In accordance with an embodiment, the PEM 115 of the DACIS 103 may be configured to receive the alternate metadata for the alternate additional content from the CPDS 107. The metadata may include, for example, Ad break locations, overlay markers/triggers, SCTE35 markers/triggers, content duration, and one or more decision points. The alternate metadata may further include a location to transition from the first additional content to the alternate additional content.

At 462, a placement of alternate additional content within the first disparate live media output stream manifest may be determined based on the associated indexed metadata and the alternate metadata. In accordance with an embodiment, the PEM 15 of the DACIS 103 may be configured to determine the placement of the alternate additional content within the first disparate live media output stream manifest based on the associated indexed metadata and the alternate metadata.

At 464, an alternate programming schedule may be generated for the first client device based on the alternate additional content and alternate metadata. In accordance with an embodiment, the PEM 15 of the DACIS 103 may be configured to generate the alternate programming schedule for the first client device, such as the client device 132 a, based on the alternate additional content and alternate metadata.

At 466, a final disparate live output stream manifest may be published for the first client device based on the generated alternate programming schedule. In accordance with an embodiment, the PEM 15 of the DACIS 103 may be configured to publish the final disparate live output stream manifest for the first client device, such as the client device 132 a, based on the generated alternate programming schedule.

In accordance with an embodiment, the final disparate live output stream manifest for the first client device may be generated based on one of the pre-defined conversion modes. The pre-defined conversion modes may correspond to pre-encoded media assets to live stream mode, pre-encoded media assets to live stream mode with scalable architecture, a live stream to live stream mode, and a mixed mode corresponding to switches between pre-encoded media assets and live streams.

In accordance with an embodiment, during playout, the first additional content may be transitioned to the alternate additional content based on one or more transition parameters. The one or more transition parameters may comprise one or more parameters from the first manifest request, current state of the first disparate live media output stream manifest determined based on accessibility, regular update, and suitable encoding, digital rights management, and compatibility with the first client device, rules provided by a stream owner operator, and user preferences defined in the repository of schedules, rights, and user preferences database 144.

As described above in FIGS. 4A and 4B, the published final disparate live output stream manifest may be transmitted to the media player of the first client device for playback of the final disparate live media output stream. Accordingly, the first client device begins or continues the playback of the final disparate live media output stream.

In an alternate embodiment, at 454, the stream selection service 142 may be configured to select a second disparate live media output stream according to accessibility of the first disparate live media output stream in case the set of criteria associated with the first disparate live media output stream is not satisfied. The stream selection service 142 may be configured to select the second disparate live media output stream according to rules provided by a stream owner/operator and user preferences defined in the repository of schedules, rights, and user preferences database 144. The operations that follow may be performed in a similar manner, as the operations for the first disparate live media output stream are performed.

FIG. 5A is a conceptual diagram illustrating an example of a hardware implementation for a media packaging and distribution system 102 employing a processing system for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, in accordance with an exemplary embodiment of the disclosure. Referring to FIG. 5, the hardware implementation shown by a representation 500 for the media packaging and distribution system 102 employs a processing system 502 for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, in accordance with an exemplary embodiment of the disclosure, as described herein. In some examples, the processing system 502 may comprise one or more hardware processors 504, a non-transitory computer-readable medium 506, a bus 508, a bus interface 510, and a transceiver 512. FIG. 5A further illustrates the DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine 114, PEM 115, indexing and storage system 116, the stream selection service 142, and the repository of schedules, rights, and user preferences database 144, as described in detail in FIGS. 1A and 1B.

The hardware processor 504 may be configured to manage the bus 508 and general processing, including the execution of a set of instructions stored on the non-transitory computer-readable medium 506. The set of instructions, when executed by the processor 504, causes the media packaging and distribution system 102 to execute the various functions described herein for any particular apparatus. The hardware processor 504 may be implemented, based on a number of processor technologies known in the art. Examples of the hardware processor 504 may be a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processors or control circuits.

The non-transitory computer-readable medium 506 may be used for storing data that is manipulated by the processor 504 when executing the set of instructions. The data is stored for short periods or in the presence of power. The non-transitory computer-readable medium 506 may also be configured to store data for one or more of the DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine 114, PEM 115, indexing and storage system 116, the stream selection service 142, and the repository of schedules, rights, and user preferences database 144.

The bus 508 is configured to link together various circuits. In this example, the media packaging and distribution system 102 employing the processing system 502 and the non-transitory computer-readable medium 506 may be implemented with bus architecture, represented generally by bus 508. The bus 508 may include any number of interconnecting buses and bridges depending on the specific implementation of the media packaging and distribution system 102 and the overall design constraints. The bus interface 510 may be configured to provide an interface between the bus 508 and other circuits, such as, transceiver 512, and external devices, such as source device 118, external data source 120, and client devices 132 a, . . . , 132 n.

The transceiver 512 may be configured to provide a communication of the media packaging and distribution system 102 with various other apparatus, such as the Ad decisioning servers 106 a, . . . , 106 n, the consumer devices 110 a, . . . , 110 n, such as the client devices 132 a, . . . , 132 n, the external data source 120, and the source device 118, via the network 108. The transceiver 512 may communicate via wireless communication with networks, such as the Internet, the Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (WLAN) and/or a metropolitan area network (MAN). The wireless communication may use any of a plurality of communication standards, protocols and technologies, such as Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Long Term Evolution (LTE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), and/or Wi-MAX.

It should be recognized that, in some embodiments of the disclosure, one or more components of FIG. 5A may include software whose corresponding code may be executed by at least one processor, for across multiple processing environments. For example, the DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine 114, PEM 115, indexing and storage system 116, the stream selection service 142, and the repository of schedules, rights, and user preferences database 144 may include software that may be executed across a single or multiple processing environments.

In an aspect of the disclosure, the processor 504, the non-transitory computer-readable medium 506, or a combination of both may be configured or otherwise specially programmed to execute the operations or functionality of the DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine 114, PEM 115, indexing and storage system 116, the stream selection service 142, and the repository of schedules, rights, and user preferences database 144, or various other components described herein, as described with respect to FIGS. 1A to 4D.

FIG. 5B is a conceptual diagram illustrating an example of a hardware implementation for a media packaging and distribution system 102 employing a processing system for managing a pre-encoded media asset for immediate playback, in accordance with exemplary embodiments of the disclosure. Referring to FIG. 5B, the hardware implementation shown by a representation 500A for the media packaging and distribution system 102 employs a processing system 552 for managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure, as described herein. In some examples, the processing system 552 may comprise one or more hardware processors, such as a processor 554, a non-transitory computer-readable medium 556, a bus 558, a bus interface 560, and a transceiver 562.

In accordance with an embodiment, for managing a pre-encoded media asset for immediate playback, FIG. 5B further illustrates the CDS 105, the CPDS 107, the SSAI system 109, and the repository of schedules, rights, and user preferences database 144. The SSAI system 109 may further comprise the internal manifest index 109 a, and the CPDS 107 may further comprise the content encoder/packager 107 a and the content metadata store 107 b. In accordance with an embodiment, as illustrated in FIG. 5B, the SSAI system 109 may be implemented within the DACIS 103, as described above in FIG. 1A. However, in accordance with another embodiment, not illustrated in FIG. 5B, the SSAI system 109 may be implemented separately from the DACIS 103, as described above in FIG. 1C. As the SSAI system 109 is implemented for pre-encoded media assets, the functionalities of a few components, such as the stream publishing engine 114, the PEM 115, and the stream selection service 142, utilized in conjunction with the DACIS 103 in the media packaging and distribution system 102, may not be required.

The processor 554 may be configured to manage the bus 558 and general processing, including the execution of a set of instructions stored on the non-transitory computer-readable medium 556. The set of instructions, when executed by the processor 554, causes the media packaging and distribution system 102 to execute the various functions described herein for any particular apparatus. The processor 554 may be implemented, based on several processor technologies known in the art. Examples of the processor 554 may be a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processors or control circuits.

The non-transitory computer-readable medium 556 may be used for storing data that is manipulated by the processor 554 when executing the set of instructions. The data is stored for short periods or in the presence of power. The non-transitory computer-readable medium 556 may also be configured to store data for one or more of the DACIS 103, the CDS 105, the CPDS 107, the SSAI system 109, the memory 134, and the repository of schedules, rights, and user preferences database 144.

The bus 558 is configured to link together various circuits. In this example, the media packaging and distribution system 102 employing the processing system 552 and the non-transitory computer-readable medium 556 may be implemented with bus architecture, represented generally by bus 558. The bus 558 may include any number of interconnecting buses and bridges depending on the specific implementation of the media packaging and distribution system 102 and the overall design constraints. The bus interface 560 may be configured to provide an interface between the bus 558 and other circuits, such as, transceiver 562, and external devices, such as the Ad decisioning servers 106 a, . . . , 106 n, the external data source 120, the content delivery system 130, and the client devices 132 a, . . . , 132 n.

In accordance with an embodiment, the transceiver 562 may be configured to provide a communication of the media packaging and distribution system 102 with various other apparatus, such as the Ad decisioning servers 106 a, . . . , 106 n, the external data source 120, the content delivery system 130, and the client devices 132 a, . . . , 132 n, via the network 108. The transceiver 562 may communicate via wireless communication with networks, such as the Internet, the Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (WLAN) and/or a metropolitan area network (MAN). The wireless communication may use any of a plurality of communication standards, protocols and technologies, such as Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Long Term Evolution (LTE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), and/or Wi-MAX.

It should be recognized that, in some embodiments of the disclosure, one or more components of FIG. 5B may include software whose corresponding code may be executed by at least one processor, for across multiple processing environments. For example, the DACIS 103, the CDS 105, the CPDS 107, the SSAI system 109, the memory 134, and the repository of schedules, rights, and user preferences database 144 may include software that may be executed across a single or multiple processing environments.

In an aspect of the disclosure, the processor 554, the non-transitory computer-readable medium 556, or a combination of both may be configured or otherwise specially programmed to execute the operations or functionality of the DACIS 103, the CDS 105, the CPDS 107, the SSAI system 109, the memory 134, and the repository of schedules, rights, and user preferences database 144, or various other components described herein, as described with respect to FIGS. 1A, 1C, 1D, 6A to 6C, and 7A to 7E.

FIG. 6A illustrates a first exemplary scenario associated with managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure. Referring to FIG. 6A, there is illustrated a first exemplary scenario 600A that corresponds to a fast start delivery model for segmented web video. In accordance with the first exemplary scenario 600A, there is illustrated a first pre-encoded media asset 602 generated for the first client device, such as the client device 132 a. There is shown a plurality of indexed programming content segments, such as PS 1, . . . , PS Last, and two sets of segments of non-programming content, for example advertisements, in the first pre-encoded media asset 602. A first ad break is at a location L1 between the programming content segments PS 50 and PS 51, and a second ad break is at a location L2 between the programming content segments PS 110 and PS 111 in the first pre-encoded media asset 602.

In accordance with a first use case 604, the client device 132 a may be an old client with limited player integration with the SSAI system 109. Further, the client device 132 a may be incompatible with the required protocol version of modern streaming protocols, such as HLS and DASH, implemented for the SSAI system 109. In such a use case, to ensure smooth and immediate video playback of the first pre-encoded media asset 602 at the client device 132 a, the SSAI system 109 may communicate an initial pre-encoded media asset manifest, such as Manifest 1, comprising an initial set of programming content segments, such as PS 1, . . . , PS 3, to the client device 132 a. The size of the initial set of programming content segments, i.e., three programming content segments, is verified to be equal to the capacity of the playback buffer (typically 3) in the media player of the client device 132 a. The client device 132 a may download and buffer the initial set of programming content segments, i.e., PS 1, . . . , PS 3, before the playback. While the client device 132 a is downloading the initial set of programming content segments and begins an immediate playback, the SSAI system 109 may insert the non-programming content, such as advertisements, in the pre-encoded media asset manifest. Meanwhile, the client device 132 a may generate a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 2, after a specified time duration controlled by the player-system integration. In response to the subsequent manifest request, as the insertion of the advertisements is not yet completed, the SSAI system 109 may add additional content segments, such as PS 4 and PS 5, to the initial pre-encoded media asset manifest, such as Manifest 1, and generate an updated pre-encoded media asset manifest, such as Manifest 2. The SSAI system 109 may communicate the updated pre-encoded media asset manifest, such as Manifest 2, comprising updated set of programing content segments, such as PS 1, . . . , PS 5, to the client device 132 a. The client device 132 a continues the playback and again generates a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 3, after a specified time duration controlled by the player-system integration.

In response to the subsequent manifest request, as the insertion of the advertisements is completed, the SSAI system 109 may add remaining programming content segments, such as PS 6, . . . , PS Last. The SSAI system 109 may further stitch the set of non-programming content segments, such as NPS 1, . . . , NPS 3, of a first advertisement at the location L1 between the programming content segments PS 50 and PS 51, and a set of non-programming content segments, such as NPS 4, . . . , NPS 6, of a second advertisement at a location L2 between the programming content segments PS 110 and PS 111 and generate the final pre-encoded media asset manifest, such as Manifest 3. Accordingly, the SSAI system 109 may communicate the final pre-encoded media asset manifest, such as Manifest 3, to the client device 132 a. Further, the final pre-encoded media asset manifest, such as Manifest 3, is designated to inform the media player of the client device 132 a to cease further generation of the subsequent manifest request.

In accordance with a second use case 606, the client device 132 a may be a new client with complete player integration with the SSAI system 109. Further, the client device 132 a may be compatible with the required protocol version of modern streaming protocols, such as HLS and DASH. In such a use case, to ensure smooth and immediate video playback of the first pre-encoded media asset 602 at the client device 132 a, the SSAI system 109 may communicate an initial pre-encoded media asset manifest, such as Manifest 1, comprising an initial set of programming content segments, such as PS 1, . . . , PS 50, up to a first ad break location, such as location L1, marked for insertion of the first advertisement.

The client device 132 a may download and buffer the initial set of programming content segments, i.e., PS 1, . . . , PS 50, before the playback. While the client device 132 a is downloading the initial set of programming content segments and begins an immediate playback from the beginning of the playback buffer, the SSAI system 109 may insert the non-programming content, such as the first advertisement at the location L1 and the second advertisement at the location L2, in the pre-encoded media asset manifest. The client device 132 a may generate a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 2, after a specified time duration controlled by the player-system integration. In response to the subsequent manifest request, as the insertion of the advertisements is completed, the SSAI system 109 may add remaining programming content segments, such as PS 51, . . . , PS Last. The SSAI system 109 may further stitch a set of non-programming content segments, such as NPS 1, . . . , NPS 3, of the first advertisement at the location L1 between the programming content segments PS 50 and PS 51, and another set of non-programming content segments, such as NPS 4, . . . , NPS 6, of the second advertisement at the location L2 between the programming content segments PS 110 and PS 111 in the final pre-encoded media asset manifest, such as Manifest 2, as the defined criterion of completion of advertisement insertion is met. Accordingly, the SSAI system 109 may communicate the final pre-encoded media asset manifest, such as Manifest 2, to the client device 132 a. Further, the final pre-encoded media asset manifest, such as Manifest 2, is designated to inform the media player of the client device 132 a to cease further generation of the subsequent manifest request.

FIG. 6B illustrates a second exemplary scenario associated with managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure. Referring to FIG. 6B, there is illustrated a second exemplary scenario 600B that corresponds to a fast start delivery model for segmented web video with enhanced features. In accordance with the second exemplary scenario 600B, there is illustrated a second pre-encoded media asset 612 generated for the first client device, such as the client device 132 a. There is shown a plurality of indexed programming content segments, such as PS 1, . . . , PS Last, and a segment of non-scheduled programming content and/or non-programming content, for example an advertisement, in the second pre-encoded media asset 612. An ad break is at a location L1 between the programming content segments, such as PS 70 and PS 71, in the second pre-encoded media asset 612. There are further shown segments of enhanced features, hereinafter referred to as a plurality of event-based programming content segments, such as PSR 1, . . . , PSR End, in the second pre-encoded media asset 612. An example of one of the enhanced features may be previous episode recap, as illustrated in the second pre-encoded media asset 612. The previous episode recap may be skipped-ahead based on an input received from the client device 132 a.

In accordance with a first use case 614, the client device 132 a may be an old client with limited player integration with the SSAI system 109. Further, the client device 132 a may be incompatible with the required protocol version of modern streaming protocols, such as HLS and DASH. In such a use case, to ensure smooth and immediate video playback of the second pre-encoded media asset 612 at the client device 132 a, the SSAI system 109 may communicate an initial pre-encoded media asset manifest, such as Manifest 1, comprising an initial set of event-based programming content segments, such as PSR 1, . . . , PSR 3, to the client device 132 a. The size of the initial set of event-based programming content segments, i.e., three programming content segments, is verified to be equal to the capacity of the playback buffer (typically 3) in the media player of the client device 132 a. The client device 132 a may generate a subsequent manifest request to update the initial pre-encoded media asset manifest, i.e. Manifest 1. In response to the subsequent manifest request, the SSAI system 109 may add remaining event-based programming content segments, such as PSR 4, . . . , PSR Last, and additional content segments, such as PSR End+1, . . . , PSR End+3 in the updated pre-encoded media asset manifest, such as Manifest 2. The size of the additional content segments, i.e., three programming content segments, is verified to be equal to the capacity of the playback buffer (typically 3) in the media player of the client device 132 a. Thus, the updated pre-encoded media asset manifest, i.e., Manifest 2, includes all of the event-based programming content segments through the marked locations eligible for skipping plus a few additional content segments equal to the capacity of the playback buffer (typically 3) in the media player of the client device 132 a. The SSAI system 109 may return the updated pre-encoded media asset manifest, i.e. Manifest 2 to the client device 132 a for an immediate playback. Accordingly, the client device 132 a may be allowed to skip the event-based programming content segments, such as PSR 1, . . . , PSR Last, and begin the immediate playback from a segment, i.e., PSR End+1, after a marked end location of the plurality of event-based programming content segments, i.e., PSR End, upon receipt of an input from the client device 132 a to skip the event-based programming content segments, i.e., PSR 1, . . . , PSR End. The client device 132 a continues the playback and again generates a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 3, after a specified time duration controlled by the player-system integration.

In response to the subsequent manifest request, as the insertion of the advertisements is completed, the SSAI system 109 may add remaining programming content segments, such as till PS Last. The SSAI system 109 may further stitch the set of non-programming content segments, such as NPS 1, . . . , NPS 3, of an advertisement at the location L1 between the programming content segments PS 70 and PS 71, in the final pre-encoded media asset manifest, such as Manifest 3, as the defined criterion of completion of advertisement insertion is met. Accordingly, the SSAI system 109 may communicate the final pre-encoded media asset manifest, such as Manifest 3, to the client device 132 a. Further, the final pre-encoded media asset manifest, such as Manifest 3, is designated to inform the media player of the client device 132 a to cease further generation of the subsequent manifest request.

In accordance with a second use case 616, the client device 132 a may be a new client with complete player integration with the SSAI system 109. Further, the client device 132 a may be compatible with the required protocol version of modern streaming protocols, such as HLS and DASH. In such a use case, to ensure smooth and immediate video playback of the second pre-encoded media asset 612 at the client device 132 a, the SSAI system 109 may communicate an initial pre-encoded media asset manifest, such as Manifest 1, comprising event-based programming content segments, i.e., PSR 1, . . . , PSR End, and additional content segments, such as PSR End+1, . . . , PSR End+3, to the client device 132 a.

Accordingly, the client device 132 a may be allowed to begin the immediate playback from a segment, i.e., PSR End+1, after a marked end location of the plurality of event-based programming content segments, i.e., PSR End, upon receipt of an input from the client device 132 a to skip the event-based programming content segments, i.e., PSR 1, . . . , PSR End. The client device 132 a continues the playback and again generates a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 2, after a specified time duration controlled by the player-system integration.

In response to the subsequent manifest request, as the insertion of the advertisements is completed, the SSAI system 109 may add remaining programming content segments, such as till PS Last. The SSAI system 109 may further stitch the set of non-programming content segments, such as NPS 1, . . . , NPS 3, of an advertisement at the location L1 between the programming content segments PS 70 and PS 71, in the final pre-encoded media asset manifest, such as Manifest 2, as the defined criterion of completion of advertisement insertion is met. Accordingly, the SSAI system 109 may communicate the final pre-encoded media asset manifest, such as Manifest 2, to the client device 132 a. Further, the final pre-encoded media asset manifest, such as Manifest 2, is designated to inform the media player of the client device 132 a to cease further generation of the subsequent manifest request.

FIG. 6C illustrates a third exemplary scenario associated with managing a pre-encoded media asset for immediate playback, in accordance with an exemplary embodiment of the disclosure. Referring to FIG. 6C, there is illustrated a third exemplary scenario 600C that corresponds to a fast start delivery model for segmented web video with early ad break. In accordance with the third exemplary scenario 600C, there is illustrated a third pre-encoded media asset 622 generated for the first client device, such as the client device 132 a. There is shown a plurality of indexed programming content segments, such as PS 1, . . . , PS Last, and two sets of segments of non-scheduled programming content and/or non-programming content, for example advertisements, in the third pre-encoded media asset 622. A first ad break occurs early and is at a location L1 between the programming content segments PS 4 and PS 5, and a second ad break is at a location L2 between the programming content segments PS 80 and PS 81 in the third pre-encoded media asset 622.

In accordance with a first use case 624, the client device 132 a may be an old client with limited player integration with the SSAI system 109. Further, the client device 132 a may be incompatible with the required protocol version of modern streaming protocols, such as HLS and DASH. In such a use case, to ensure smooth and immediate video playback of the third pre-encoded media asset 622 at the client device 132 a, the SSAI system 109 may communicate an initial pre-encoded media asset manifest, such as Manifest 1, comprising an initial set of programming content segments, such as PS 1, . . . , PS 3, to the client device 132 a. The size of the initial set of programming content segments, i.e., three programming content segments, is verified to be equal to the capacity of the playback buffer (typically 3) in the media player of the client device 132 a. The client device 132 a may download and buffer the initial set of programming content segments, i.e., PS 1, . . . , PS 3, before the playback. While the client device 132 a is downloading the initial set of programming content segments and begins an immediate playback, the SSAI system 109 may insert the non-programming content, such as advertisements, and programming content as well in the pre-encoded media asset manifest. Meanwhile, the client device 132 a may generate a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 2, after a specified time duration controlled by the player-system integration. In response to the subsequent manifest request, as the insertion of the advertisements is not yet completed, the SSAI system 109 may add additional content segments, such as PS 4 and PS 5, and a set of non-programming content segments, such as NPS 1, . . . , NPS 3, of the first advertisement to the initial pre-encoded media asset manifest, such as Manifest 1 and generate an updated pre-encoded media asset manifest, such as Manifest 2. The SSAI system 109 may communicate the updated pre-encoded media asset manifest, such as Manifest 2, comprising an updated set of programming content segments, such as PS 1, . . . , PS 5, and the set of non-programming content segments, such as NPS 1, . . . , NPS 3, of the first advertisement to the client device 132 a. The client device 132 a continues the playback and again generates a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 3, after a specified time duration controlled by the player-system integration.

In response to the subsequent manifest request, as the insertion of the advertisements is completed, the SSAI system 109 may add remaining programming content segments, such as PS 6, . . . , PS Last. The SSAI system 109 may further stitch a set of non-programming content segments, such as NPS 4, . . . , NPS 6, of the remaining second advertisement at a location L2 between the programming content segments PS 80 and PS 81, and generate a final pre-encoded media asset manifest, such as Manifest 3, as the defined criterion of completion of advertisement insertion is met. Accordingly, the SSAI system 109 may communicate the final pre-encoded media asset manifest, such as Manifest 3, to the client device 132 a. Further, the final pre-encoded media asset manifest, such as Manifest 3, is designated to inform the media player of the client device 132 a to cease further generation of the subsequent manifest request.

In accordance with a second use case 626, the client device 132 a may be a new client with complete player integration with the SSAI system 109. Further, the client device 132 a may be compatible with the required protocol version of modern streaming protocols, such as HLS and DASH. In such a use case, to ensure smooth and immediate video playback of the third pre-encoded media asset 622 at the client device 132 a, the SSAI system 109 may communicate an initial pre-encoded media asset manifest, such as Manifest 1, comprising an initial set of programming content segments, such as PS 1, . . . , PS 5, and a set of non-programming content segments, such as NPS 1, . . . , NPS 3, of the first advertisement at the location L1 between the programming content segments, such as PS 4 and PS 5.

The client device 132 a may download and buffer the initial set of programming content segments, i.e., PS 1, . . . , PS 5, and the set of non-programming content segments, such as NPS 1, . . . , NPS 3, before the playback. While the client device 132 a is downloading the initial set of programming and non-programming content segments and begins an immediate playback, the SSAI system 109 may insert the remaining programming content and non-programming content, such as advertisements, in the pre-encoded media asset manifest. The client device 132 a may generate a subsequent manifest request for an updated pre-encoded media asset manifest, such as Manifest 2, after a specified time duration controlled by the player-system integration. In response to the subsequent manifest request, as the insertion of the advertisements is completed, the SSAI system 109 may add remaining programming content segments, such as PS 6, . . . , PS Last. The SSAI system 109 may further stitch a set of non-programming content segments, such as NPS 4, . . . , NPS 6, of the second advertisement at the location L2 between the programming content segments, such as PS 80 and PS 81, in a final pre-encoded media asset manifest, such as Manifest 2, as the defined criterion of completion of advertisement insertion is met. Accordingly, the SSAI system 109 may communicate the final pre-encoded media asset manifest, such as Manifest 2, to the client device 132 a. Further, the final pre-encoded media asset manifest, such as Manifest 2, is designated to inform the media player of the client device 132 a to cease further generation of the subsequent manifest request.

In accordance with various embodiments as described in the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, the number of the updated pre-encoded media asset manifests (for both use cases) may be based on various factors, such as number of content placement opportunities in the first set of content placement opportunities, how many viewers need to respond for insertion in such number of content placement opportunities, a response from one Ad decisioning server to redirect to another Ad decisioning server for insertion of advertisements in the first set of content placement opportunities based on separation and capping rules, and/or user-defined configurable parameters on how long (such as 5 seconds) to wait for a response from a third-party Ad decisioning server. It may not be mandatory that the SSAI system 109 responds to the client device 132 a with updated pre-encoded media asset manifests in each response. The SSAI system 109 may issue a notification indicating no change in the previously communicated pre-encoded media asset manifest if the SSAI system 109 is still waiting for the non-programming content from an Ad decisioning server or still inserting non-programming content in the previously updated pre-encoded media asset manifest. Thus, the number of manifests indicated in both the use cases in each of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C is merely for exemplary purposes and should not be construed to be limiting or deviating from the scope of the disclosure.

FIGS. 7A to 7E collectively depict a flowchart illustrating exemplary operations for managing a pre-encoded media asset for immediate playback by the SSAI system 109 of FIG. 1D, in accordance with an exemplary embodiment of the disclosure. Specifically, flowchart 700A depicts a method for generating a pre-encoded media asset for distribution, in accordance with an embodiment of the disclosure. Flowcharts 700B to 700E collectively depict a method for generating a set of pre-encoded media asset manifests for immediate playback by the SSAI system 109 of FIG. 1D, in accordance with an exemplary embodiment of the disclosure.

Referring to flowchart 700A, at 702, a pre-encoded media asset comprising a plurality of programming content segments may be generated for distribution. In accordance with an embodiment, the content encoder/packager 107 a may be configured to generate the pre-encoded media asset comprising a plurality of programming content segments for distribution. In accordance with various embodiments, without deviating from the scope of the disclosure, the distribution may be web distribution, broadcast, or satellite distribution.

The pre-encoded media asset generated for the distribution, for example, Internet distribution, may comprise a sequence of short duration programming content segments added to a pre-encoded media asset manifest. The short duration programming content segments may be separate physical files or pointers (real or to be calculated) to the short media content segments inside a larger file. In accordance with an embodiment, the content encoder/packager 107 a may be directly coupled to the indexing and storage system (not shown in FIG. 1C).

In accordance with various embodiments, corresponding to different exemplary scenarios, the content encoder/packager 107 a may generate different pre-encoded media assets, each comprising a plurality of programming content segments, such as PS 1, . . . , PS Last. Such exemplary scenarios may correspond to, for example, a fast start delivery model for segmented web video, a fast start delivery model for segmented web video with enhanced features, and a fast start delivery model for segmented web video with early ad break.

The content encoder/packager 107 a may be configured to determine a package that includes a media content and associated metadata. The media content may correspond to one or more of programming content segments of the pre-encoded media assets transcoded to different types of streams for different types of devices, such as a TV or a mobile device, and marked with Nielson markers. The content encoder/packager 107 a may encode and package such media content into required on-demand formats for delivery to the client devices 132 a, . . . , 132 n. Based on such a package, one or more encoded media assets may be dynamically generated for playout to one or more media players communicatively coupled through the content delivery system 130.

The content encoder/packager 107 a may be configured to publish the one or more encoded media assets, as one or more pre-encoded media assets, in real-time or near real-time in the content delivery system 130. In accordance with an embodiment, the resulting converted output, i.e., one or more encoded media assets, that are generated by the content encoder/packager 107 a, may be communicated to the indexing and storage system 116. The content encoder/packager 107 a may also support a robust interface (for example, ADI) that defines the on-demand duration of the individual segments as well as encryption requirements and a service type to link for ad insertion. Various formats of the pre-encoded media asset manifests may include, but are not limited to, HLS and DASH.

At 704, based on metadata retrieved from the content metadata store 107 b, the plurality of programming content segments may be adjusted in the pre-encoded media asset. In accordance with an embodiment, the content encoder/packager 107 a may be configured to adjust the plurality of programming content segments in the pre-encoded media asset based on the metadata retrieved from the content metadata store 107 b. In other words, the metadata from the content metadata store 107 b may be used to condition the pre-encoded media asset to provide clean locations in the pre-encoded media asset manifest where ads can be inserted. In accordance with another embodiment, the metadata from the content metadata store 107 b may be used to condition the pre-encoded media asset to provide clean locations for event-based programming content, such as opening credits and previous episode recaps, so that such event-based programming content can be skipped when the customer is binging multiple episodes.

Examples of the metadata may include a pre-encoded media asset identifier, a title of the pre-encoded media asset, type of the pre-encoded media asset (such as movie series (season episode number)), genre, plot summary, duration, advertisement break locations, credit locations, scene descriptions, a short summary of the programming content segments, a short summary of ideal advertisement placements within the pre-encoded media asset, a file format, DRM, encryption information, length of the pre-encoded media asset, a date and/or time the pre-encoded media asset was added to the catalog of pre-encoded media assets, a new item indicator for the pre-encoded media asset (for example, a new pre-encoded media asset that became available within the last 24 hours, last few days, last week, and/or the like), and/or a pre-encoded asset class (for example, a television show, a cartoon program, a movie, a news media, an episode, a game, a curated clip, a recorded sports event, interactive media, and/or the like). Other forms of metadata may be utilized without departing from the spirit and scope of the various embodiments of the disclosure.

In accordance with an embodiment, the adjustment of the plurality of programming content segments may provide a first set of content placement opportunities where the plurality of non-programming content may be inserted in the pre-encoded media asset manifest. In accordance with various examples, the non-programming content may correspond to ad breaks or promotional content. The first set of content placement opportunities may correspond to, for example, non-programming indicators (such as indicators corresponding to commercial advertisements, non-commercial advertisements, paid advertisements, public service advertisements, and/or promotional material). In accordance with another embodiment, the adjustment of the plurality of programming content segments may provide a second set of content placement opportunities where event-based programming content may occur in the pre-encoded media asset manifest. In accordance with various examples, the event-based programming content may correspond to an identifier corresponding to an event related to the content. The second set of content placement opportunities correspond to, for example, event markers (such as markers corresponding to opening credits, closing credits, previous episode recaps, timing, and/or other similar skippable media content).

In accordance with an exemplary embodiment, with reference to the first exemplary scenario 600A in FIG. 6A, the content encoder/packager 107 a may adjust the plurality of programming content segments, such as PS 1, . . . , PS Last, based on the metadata. Accordingly, the first ad break is determined to be at a location L1 between the programming content segments PS 50 and PS 51, and a second ad break is at a location L2 between the programming content segments PS 110 and PS 111, as illustrated in the first pre-encoded media asset 602.

In accordance with another exemplary embodiment, with reference to the second exemplary scenario 600B in FIG. 6B, the content encoder/packager 107 a may adjust the plurality of event-based programming content segments, such as PSR 1, . . . , PSR End, and programming content segments, such as PS 1, . . . , PS Last, based on the metadata. Accordingly, the ad break is determined to be at a location L1 between the programming content segments PS 70 and PS 71, as illustrated in the second pre-encoded media asset 612.

In accordance with yet another exemplary embodiment, with reference to the third exemplary scenario 600C in FIG. 6C, the content encoder/packager 107 a may adjust the plurality of programming content segments, such as PS 1, . . . , PS Last, based on the metadata. Accordingly, the first ad break is determined to be early at a location L1 between the programming content segments PS 4 and PS 5, and a second ad break is at a location L2 between the programming content segments PS 80 and PS 81, as illustrated in the third pre-encoded media asset 622.

At 706, timestamps of the first set of content placement opportunities and the second set of content placement opportunities may be stored in the metadata upon the generation of the pre-encoded media asset. In accordance with an embodiment, the content encoder/packager 107 a may be configured to store the timestamps of the first set of content placement opportunities and the second set of content placement opportunities in the metadata upon the generation of the pre-encoded media asset. In other words, the time of the ad locations, such as L1 and L2, and the event-based programming content may be noted by the content encoder/packager 107 a and may be provided back to the content metadata store 107 b once the pre-encoded media asset is created.

At 708, a start location and an end location of each of first set of content placement opportunities and second set of content placement opportunities may be marked in the pre-encoded media asset manifest. In accordance with an embodiment, the content encoder/packager 107 a may be configured to mark the start location and the end location of each of the first set of content placement opportunities and the second set of content placement opportunities in the pre-encoded media asset manifest. In other words, the content encoder/packager 107 a may be configured to mark the ad locations and the event-based programming content in the pre-encoded media asset manifest itself to avoid the need for extra calls and calculations during the ad insertion process or for identification of such event-based programming content, respectively.

For example, with reference to FIGS. 6A to 6C, the start location of the first ad break determined to be at a location L1 may be marked as L1 _(start) and the end location may be marked as L1 _(End) in the pre-encoded media asset manifests of each of the first pre-encoded media asset 602, the second pre-encoded media asset 612, and the third pre-encoded media asset 622. With reference to FIG. 6B, the start location of the event-based programming content may be marked as E_(start) which may be zero, as the event-based programming content, for example, previous episode recap occurs at the beginning of the second pre-encoded media asset 612. The end location may be marked as E_(End) based on a time offset associated with the event-based programming content.

At 710, the pre-encoded media asset manifest may be stored in a content delivery system and/or internal manifest index. In accordance with an embodiment, the content encoder/packager 107 a may be configured to store the pre-encoded media asset manifest in the content delivery system 130 and/or the internal manifest index 109 a. In other words, in one example embodiment, the content encoder/packager 107 a may push the pre-encoded media asset manifest to the content delivery system 130. In another example embodiment, the content encoder/packager 107 a may register the pre-encoded media asset manifest with the SSAI system 109 and store the pre-encoded media asset manifest in the internal manifest index 109 a.

Referring to flowcharts 700B to 700E, at 714, an initial manifest request may be received from a first client device to view a pre-encoded media asset. In accordance with an embodiment, the SSAI system 109 may be configured to receive the initial manifest request from the first client device, such as the client device 132 a, to view a pre-encoded media asset. In other words, when the client device 132 a requests to view a desired pre-encoded media asset, the initial manifest request is directed to the SSAI system 109. Various examples of the client device 132 a may include, but are not limited to, a personal computer, a smartphone, a tablet, an over-the-top (OTT) set-top, or a hybrid set-top on which a user launches a web page, an application, or a service to view the pre-encoded media asset, such as a VOD.

In accordance with an embodiment, the initial manifest request may be associated with one of the various scenarios, as described above in FIGS. 6A to 6C, that correspond to an immediate playback of a pre-encoded media asset. In accordance with an embodiment, the initial manifest request may include additional data, such as device identifier of the first client device, device type of the first client device, user preferences, preferred date and time of viewing the pre-encoded media asset, and/or capacity of the playback buffer of the first client device.

At 716, a pre-encoded media asset manifest, based on the received initial manifest request, may be accessed from the content delivery system 130 or the internal manifest index 109 a. In accordance with an embodiment, the SSAI system 109 may be configured to access the pre-encoded media asset manifest, based on received initial manifest request, from the content delivery system 130 or the internal manifest index 109 a. In one example embodiment, the SSAI system 109 requests a pre-encoded media asset manifest corresponding to the desired pre-encoded media asset from the content delivery system 130 on behalf of the first client device, such as the client device 132 a, based on the additional data included in the received initial manifest request. In another example embodiment, if the pre-encoded media asset manifest corresponding to the desired pre-encoded media asset was previously registered, the SSAI system 109 accesses the pre-encoded media asset manifest from the internal manifest index 109 a.

At 718, an instruction, based on targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules, may be received. In accordance with an embodiment, the SSAI system 109 may be configured to receive an instruction, based on the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules. In accordance with an exemplary embodiment, the SSAI system 109 may be instructed, via the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules, for determining whether all the non-scheduled programming content and/or non-programming content will be inserted as a single response to the first client device, such as the client device 132 a, as per the operation at 722. In accordance with another exemplary embodiment, the SSAI system 109 may be instructed, via the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules, for returning an initial pre-encoded media asset manifest, inclusive of or independent of the non-scheduled programming content and/or non-programming content, to the first client device, such as the client device 132 a. The decision about including or excluding the non-scheduled programming content and/or non-programming content may be based on capability of the client device 132 a that may be determined by the operation at 724.

The targeting and non-targeting parameters may comprise metadata associated with the pre-encoded media asset, data associated with the first client device, and/or data associated with scheduling window of the pre-encoded media asset. Non-limiting examples of the metadata may include advertisement break locations, enhanced programming event markers, locations for inserting non-scheduled programming content in the pre-encoded media asset. Non-limiting examples of the data associated with the first client device may include session identifiers, date and time of client requests, length/duration of client session (such as 4-hour session or 1-hour session), and date and time of viewing a media content. Non-limiting examples of data associated with the scheduling window of the pre-encoded media asset (that is to be played) may include business rules associated with the scheduling window (for example, if the pre-encoded media asset is to be viewed the next day, what would be the 12^(th) asset when played back), availability of a pre-encoded media asset before playback, or promotional content in the pre-encoded media asset that is to be dynamically included or automatically updated once the playback of programming segments begins. The external system may correspond to one or more of the Ad decisioning servers 106 a, . . . , 106 n. The set of pre-determined rules may correspond to rules about what is to be inserted as non-scheduled programming content (provided by the CDS 105) and/or non-programming content (provided by the Ad decisioning servers 106 a, . . . , 106 n).

At 720, the type of instruction may be identified. In accordance with an embodiment, the SSAI system 109 may be configured to identify the type of the instruction. In one exemplary embodiment, the type of instruction may be a first instruction corresponding to insertion of all the non-scheduled programming content and/or non-programming content upon the initial and final response to the first client device, such as the client device 132 a, for playback the pre-encoded media asset. In such an embodiment, the control passes to the operation at 722. In one exemplary embodiment, the type of instruction may be a second instruction corresponding to enabling the immediate playback of the pre-encoded media asset at the first client device. In such an embodiment, the control passes to the operation at 724.

At 722, each non-scheduled programming content and/or non-programming content may be inserted in the pre-encoded media asset manifest as an initial and final response to the initial manifest request for the playback of the pre-encoded media asset at the first client device in accordance with the first instruction, based on the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules. In accordance with an embodiment, in accordance with the first instruction, the SSAI system 109 may be configured to insert each non-scheduled programming content and/or non-programming content in the pre-encoded media asset manifest as an initial and final response to the initial manifest request for the playback of the pre-encoded media asset at the first client device, such as the client device 132 a, in accordance with the first instruction, based on the targeting and/or non-targeting parameters, the external system, and/or the set of pre-determined rules.

In such an embodiment, a final pre-encoded media asset manifest may be generated directly as a single response to the client device 132 a. Thereafter, the control passes to the operation at 742 in flowchart 700D. The operations at 742 followed by the operations at 744, 746, and 748 may be executed without the requirement of any subsequent manifest request.

At 724, capability of the first client device may be determined based on the targeting and/or non-targeting parameters, the external system and/or the set of pre-determined rules. In accordance with an embodiment, the SSAI system 109 may be configured to determine the capability of the first client device, such as the client device 132 a, based on the targeting and/or non-targeting parameters, the external system and/or the set of pre-determined rules. The capability of the first client device may correspond to an extent of player integration with the system and compatibility of the first client device, such as the client device 132 a, with a required protocol version. The extent of the player integration may control various functionalities, for example, informing the media player of the first client device to start playback from the beginning of the pre-encoded media asset, controlling when the media player should request updated pre-encoded media manifests, and presenting data indicating the entire pre-encoded media asset duration, and the like. The compatibility of the first client device, such as the client device 132 a, with the required protocol version, such as HLS v7. Based on the compatibility of the first client device with the required protocol version, various #tags, features and attributes, such as #EXT-X-DATERANGE, #EXT-X-SESSION-KEY, E-AC-3 codec support, and SCTE-35 signalling, may be supported.

At 726, the extent of player integration with system and compatibility with required protocol may be determined. In accordance with an embodiment, the SSAI system 109 may be configured to determine the extent of the player integration with the SSAI system 109 and compatibility with the required protocol. In one exemplary embodiment, the extent of player integration with the SSAI system 109 is limited and the first client device, such as the client device 132 a, is incompatible with the required protocol version. In such an embodiment, the control passes to the operation at 728. In another exemplary embodiment, the extent of player integration with the SSAI system 109 is complete and the first client device, such as the client device 132 a, is compatible with the required protocol version, In such an embodiment, the control passes to the operation at 730.

At 728, in case the extent of the player integration with the system is limited and the first client device is incompatible with the required protocol, an initial pre-encoded media asset manifest may be generated that comprises an initial set of programming content segments based on the receipt of an initial manifest request from the first client device. The size of the initial set of programming content segments is verified to be equal to capacity of the playback buffer in the media player of the first client device. In accordance with an embodiment, the SSAI system 109 may be configured to generate, based on the receipt of an initial manifest request from the first client device (such as the client device 132 a), the initial pre-encoded media asset manifest that comprises the initial set of programming content segments. In such an embodiment, the initial pre-encoded media asset manifest may be independent of non-scheduled programming content and/or the non-programming content. The initial pre-encoded media asset manifest may enable the immediate playback of the pre-encoded media asset at the first client device in accordance with the second instruction. The initial pre-encoded media asset manifest may be based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules. An equality between the size of the initial set of programming content segments and the capacity of the playback buffer may facilitate the immediate playback at the first client device, such as the client device 132 a, from beginning of the pre-encoded media asset.

In an example, with reference to the first use case 604 of the first exemplary scenario 600A in FIG. 6A, the SSAI system 109 may generate the initial pre-encoded media asset manifest, i.e., Manifest 1, that comprises the initial set of programming content segments, such as PS 1, . . . , PS 3. In another example, with reference to the first use case 624 of the third exemplary scenario 600C in FIG. 6C, the SSAI system 109 may generate the initial pre-encoded media asset manifest, i.e., Manifest 1, that comprises the initial set of programming content segments, such as PS 1, . . . , PS 3.

At 730, in case the extent of the player integration with the system is complete and the first client device is compatible with the required protocol, an initial pre-encoded media asset manifest may be generated that comprises an initial set of programming content segments up to a first content placement opportunity from the first set of content placement opportunities marked for insertion of a first non-scheduled programming content and/or non-programming content. The initial pre-encoded media asset manifest may be generated based on the receipt of the initial manifest request from the first client device. In accordance with an embodiment, the SSAI system 109 may be configured to generate, based on the receipt of the initial manifest request from the first client device (such as the client device 132 a), the initial pre-encoded media asset manifest that comprises the initial set of programming content segments up to the first content placement opportunity marked for insertion of the non-scheduled programming content and/or the non-programming content. In such an embodiment, the initial pre-encoded media asset manifest may be independent of non-scheduled programming content and/or the non-programming content. The initial pre-encoded media asset manifest may enable the immediate playback of the pre-encoded media asset at the first client device in accordance with the second instruction. The initial pre-encoded media asset manifest may be based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules.

For example, with reference to the second use case 606 of the first exemplary scenario 600A in FIG. 6A, the SSAI system 109 may generate the initial pre-encoded media asset manifest, i.e., Manifest 1, that comprises the initial set of programming content segments, such as PS 1, . . . , PS 50 up to the first content placement opportunity, such as the first ad break at location L1, marked for insertion of the non-programming content. The control passes to the operation at 732.

In accordance with an embodiment, the SSAI system 109 may be configured to communicate a signal to the media player of the first client device, such as the client device 132 a, to start the immediate playback from beginning of the pre-encoded media asset based on the complete player integration.

In accordance with an embodiment, the SSAI system 109 may be configured to control a timing of the subsequent manifest request to be generated by the media player of the first client device, such as the client device 132 a based on the complete player integration. In other words, the complete player integration with the first client device, such as the client device 132 a, may control when the media player should request an updated pre-encoded media asset manifests, as if fast forwarding to near the end of the programming content segments communicated in the initial pre-encoded media asset manifest.

In accordance with an embodiment, the SSAI system 109 may be configured to provide data indicating an entire duration of the pre-encoded media asset to the media player of the first client device, such as the client device 132 a.

At 732, the generated initial pre-encoded media asset manifest may be communicated, as a first disparate live media output stream manifest, to the media player of the first client device via the content delivery system 130 for an immediate playback of the pre-encoded media asset. The initial pre-encoded media asset manifest may be communicated as the first disparate live media output stream manifest to the first client device based on one of pre-defined conversion modes. In accordance with an embodiment, the SSAI system 109 may be configured to communicate the generated initial pre-encoded media asset manifest, as the first disparate live media output stream manifest, to the media player of the first client device (such as the client device 132 a) via the content delivery system 130 for an immediate playback of the pre-encoded media asset.

For example, with reference to the first use cases 604, 614, and 624 and the second use case 606 as described above, the SSAI system 109 may communicate the generated initial pre-encoded media asset manifest, i.e. Manifest 1, as the first disparate live media output stream manifest, to the media player of the client device 132 a, via the content delivery system 130, for an immediate playback of the pre-encoded media assets 602, 612, and 622, respectively.

In accordance with an embodiment, the pre-defined conversion modes may correspond to a pre-encoded media assets to live stream mode or a pre-encoded media assets to live stream mode with scalable architecture. The conversion may facilitate a subsequent modification to the first disparate live media output stream. The subsequent modification may correspond to one of a user selection, a user preference, or a change in a time or geolocation-based rule.

At 734, the initial pre-encoded media asset manifest may be designated to inform the media player of the first client device to generate a subsequent manifest request. In accordance with an embodiment, the SSAI system 109 may be configured to designate the initial pre-encoded media asset manifest to inform the media player of the first client device (such as the client device 132 a) to generate the subsequent manifest request as if it were a live or an event stream. The generated subsequent manifest request may be received by the SSAI system 109 and the SSAI system 109 responds to the subsequent manifest request by updating the initial pre-encoded media asset manifest.

For example, with reference to the first use cases 604, 614, and 624 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, the SSAI system 109 may designate the respective initial pre-encoded media asset manifests, i.e., Manifest 1, to generate a subsequent manifest request for updated pre-encoded media asset manifests, i.e., Manifest 2. Similarly, with reference to the second use cases 606, 616, and 626 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, the SSAI system 109 may designate the respective initial pre-encoded media asset manifests, i.e., Manifest 1, to generate a subsequent manifest request for updated pre-encoded media asset manifests, i.e., Manifest 2.

At 736, a unique SID may be assigned to the first client device to record a session of the first client device for the subsequent manifest request or a final manifest request associated with the initial manifest request. In accordance with an embodiment, the SSAI system 109 may be configured to assign the unique SID to the first client device (such as the client device 132 a) to record a session of the first client device for the subsequent manifest request or the final manifest request associated with the initial manifest request.

At 738, receipt of information regarding each of the non-scheduled programming content and/or non-programming content from corresponding servers may be verified. In accordance with an embodiment, the SSAI system 109 may be configured to verify the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content from corresponding servers, such as the CDS 105 and one or more of the Ad decisioning servers 106 a, . . . , 106 n.

In an exemplary embodiment, the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content is verified. In such an embodiment, the control passes to the operation at 740. In another exemplary embodiment, the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content is not verified. In such an embodiment, the control loops back to operation at 738 and waits until the SSAI system 109 verifies the receipt of the required information. In such a case, the SSAI system 109 may issue a notification to the client device 132 a indicating no change in the previously communicated pre-encoded media asset manifest as the SSAI system 109 is still waiting for the non-programming content from one or more of the Ad decisioning servers 106 a, . . . , 106 n.

For example, the SSAI system 109 may verify the receipt of the information regarding each non-programming content, such as the first advertisement and/or the second advertisement, in the pre-encoded media asset, such as the first pre-encoded media asset 602, the second pre-encoded media asset 612, and/or the third pre-encoded media asset 622, from the one or more of the Ad decisioning servers 106 a, . . . , 106 n.

At 740, it may be determined whether insertion of each of the non-scheduled programming content and/or the non-programming content is complete or incomplete in the updated pre-encoded media asset manifest based on the received information. In accordance with an embodiment, the SSAI system 109 may be configured to determine whether the insertion of each of the non-scheduled programming content and/or the non-programming content is complete or incomplete in the updated pre-encoded media asset manifest based on the received information.

In an exemplary embodiment, the insertion of each of the non-scheduled programming content and/or the non-programming content is determined to be complete in the updated pre-encoded media asset manifest. In such an embodiment, the control passes to the operation at 742. In another exemplary embodiment, the insertion of each of the non-scheduled programming content and/or the non-programming content is determined to be incomplete. The SSAI system 109 may start the insertion of the non-scheduled programming content and/or the non-programming content in the updated pre-encoded media asset manifest, i.e., Manifest 2, while the client device 132 a is downloading the set of programming content segments in the previous pre-encoded media asset manifest, i.e., Manifest 1, and begins the playback. In such an embodiment, the control passes to the operation at 750 in flowchart 700E.

At 742, a final pre-encoded media asset manifest may be generated upon receipt of the subsequent manifest request from the first client device based on a defined criterion. In accordance with an embodiment, the SSAI system 109 may be configured to generate the final pre-encoded media asset manifest upon the receipt of the subsequent manifest request from the first client device, such as the client device 132 a, based on the defined criterion. The defined criterion may correspond to the determination that the insertion of the non-scheduled programming content and/or the non-programming content in the final pre-encoded media asset manifest is complete. Thus, the updated pre-encoded media asset manifest, i.e., Manifest 2, may be generated as the final pre-encoded media asset manifest when the insertion of each of the non-scheduled programming content and/or the non-programming content is completed by the time the subsequent manifest request is received by the SSAI system 109.

In accordance with an embodiment, the final pre-encoded media asset manifest may comprise remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters. For example, the Manifest 2, as illustrated in the second use case 606 of the first exemplary scenario 600A, may include the remaining programming content segments, such as PS 51, . . . , PS Last, and non-programming content segments, such as NPS 1, . . . , NPS 6. Similarly, the Manifest 2, as illustrated in the second use case 626 of the third exemplary scenario 600C, may include the remaining programming content segments, such as PS 6, . . . , PS Last, and non-programming content segments, such as NPS 4, . . . , NPS 6.

In accordance with an embodiment, the final pre-encoded media asset manifest may include references to the set of non-scheduled programming content segments and/or non-programming content segments corresponding to each non-scheduled programming content and/or non-programming content respectively, inserted at a first set of content placement opportunities defined in the metadata.

At 744, the final pre-encoded media asset manifest may be communicated to the first client device in response to the subsequent manifest request when the defined criterion is met. In accordance with an embodiment, the SSAI system 109 may be configured to communicate the final pre-encoded media asset manifest to the first client device, such as the client device 132 a, in response to the subsequent manifest request when the defined criterion is met. For example, Manifest 2, as generated in the second use cases 606 and 626 of the first exemplary scenario 600A and the third exemplary scenario 600C, respectively, is communicated by the SSAI system 109 to the client device 132 a as the final pre-encoded media asset manifest, as the insertion of the each of non-scheduled programming content is complete in the Manifest 2.

At 746, the final pre-encoded media asset manifest may be designated to inform the media player of the first client device to cease further generation of the subsequent manifest request. In accordance with an embodiment, the SSAI system 109 may be configured to designate the final pre-encoded media asset manifest to inform the media player of the first client device, such as the client device 132 a, to cease further generation of the subsequent manifest request. In other words, the final pre-encoded media asset manifest may be designated to inform the media player that there is no longer a need to request further updated pre-encoded media asset manifests.

At 748, the initial, the updated, and/or the final pre-encoded media asset manifests may be stored as a set of asset manifests corresponding to the unique SID for a designated period of time when the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content is verified, the insertion of each of the non-scheduled programming content and/or the non-programming content is determined to be complete, and the final pre-encoded media asset manifest is communicated to the first client device. In accordance with an embodiment, the SSAI system 109 may be configured to store the initial, the updated, and/or the final pre-encoded media asset manifests as a set of asset manifests corresponding to the unique SID for the designated period of time when the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content is verified, the insertion of each of the non-scheduled programming content and/or the non-programming content is determined to be complete, and the final pre-encoded media asset manifest is communicated to the first client device, such as the client device 132 a.

The set of asset manifests may be stored based on a duration of the pre-encoded media asset upon receipt of a request of a different profile from the media player of the first client device, such as the client device 132 a, based on connectivity changes of the first client device. Thereafter, the SSAI system 109 may be configured to stop all other processing related to the unique SID.

At 750, it may be determined whether the pre-encoded media asset manifest and/or the metadata include a second set of content placement opportunities. In accordance with an embodiment, the SSAI system 109 may be configured to determine whether the pre-encoded media asset manifest and/or the metadata include the second set of content placement opportunities. In an exemplary embodiment, the pre-encoded media asset manifest and/or the metadata includes the second set of content placement opportunities. In such an embodiment, the control passes to the operation at 752. In another exemplary embodiment, the pre-encoded media asset manifest and/or the metadata does not include the second set of content placement opportunities. In such an embodiment, the control passes to the operation at 756.

At 752, a plurality of event-based programming content segments and additional content segments may be added in the updated pre-encoded media asset manifest when the pre-encoded media asset manifest and/or the metadata includes the second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest. In accordance with an embodiment, the SSAI system 109 may be configured to add the plurality of event-based programming content segments and the additional content segments in the updated pre-encoded media asset manifest when the pre-encoded media asset manifest and/or the metadata includes the second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest. The size of the additional content segments matches with capacity of a playback buffer in the media player of the first client device, such as the client device 132 a. In other words, in presence of one or more markings in the pre-encoded media asset manifest or external data, such as the metadata, indicting the location of skippable items, such as opening credits, or a recap of previous episodes, the initial pre-encoded media asset manifest may include all of the programming content segments through the marked locations eligible for skipping plus a few additional content segments equal to the playback buffer in the media player of the first client device, such as the client device 132 a.

For example, with reference to the first use case 614 of the second exemplary scenario 600B in FIG. 6B, the SSAI system 109 may add event-based programming content segments, such as PSR 4, . . . , PSR End, and additional content segments, such as PSR End+1, . . . , PSR End+3, in the updated pre-encoded media asset manifest, i.e. Manifest 2. The initial pre-encoded media asset manifest, i.e. Manifest 1, comprises only three event-based programming content segments, such as PSR 1, . . . , PSR 3, and is not eligible for playback.

At 754, the media player of the first client device may be allowed to begin an immediate playback after the marked end location of the plurality of event-based programming content segments upon a receipt of an input from the first client device to skip the event-based programming content. In accordance with an embodiment, the SSAI system 109 may be configured to allow the media player of the first client device, such as the client device 132 a, to begin the immediate playback after the marked end location of the plurality of event-based programming content segments upon a receipt of an input from the first client device, such as the client device 132 a, to skip the event-based programming content. The immediate playback starts from a beginning of the additional content segments in the updated pre-encoded media asset manifest. In other words, the media player may be allowed to begin the playback after the event-based programming content segments marked as skippable if the viewer elects to skip the event-based programming. The additional segments may be needed to maintain the video buffer of the media player for a smooth playback. The control passes to the operation at 760.

For example, with reference to the first use case 614 of the second exemplary scenario 600B in FIG. 6B, the SSAI system 109 may allow the client device 132 a to begin the immediate playback from a segment, i.e., PSR End+1, after a marked end location of the plurality of event-based programming content segments, i.e., PSR End, upon receipt of an input from the client device 132 a to skip the event-based programming content segments, i.e., PSR 1, . . . , PSR End.

At 756, additional content segments corresponding to the pre-encoded media asset, the non-scheduled programming content segments and/or the non-programming content segments may be added in the updated pre-encoded media asset manifest to provide additional time duration. In accordance with an embodiment, the SSAI system 109 may be configured to add the additional content segments corresponding to the pre-encoded media asset, the non-scheduled programming content segments and/or the non-programming content segments in the updated pre-encoded media asset manifest to provide additional time duration. Such an embodiment may be realized when the SSAI system 109 determines that the pre-encoded media asset manifest and/or the metadata does not include the second set of content placement opportunities.

In an example, with reference to the first use case 604 of the first exemplary scenario 600A in FIG. 6A, the SSAI system 109 may generate the updated pre-encoded media asset manifest, i.e., Manifest 2, that comprises the additional programming content segments, such as PS 4 and PS 5 to provide additional time duration. With reference to the second use case 606 of the first exemplary scenario 600A in FIG. 6A, the SSAI system 109 may generate the updated pre-encoded media asset manifest, i.e., Manifest 2, that comprises the additional programming content segments, such as PS 51 and PS Last to provide additional time duration.

In another example, with reference to the first use case 624 of the third exemplary scenario 600C in FIG. 6C, the SSAI system 109 may generate the updated pre-encoded media asset manifest, i.e., Manifest 2, that comprises the additional programming content segments, such as PS 4 and PS 5 and also the non-programming content segments, such as NPS 1, . . . , NPS 3, which occurs early, i.e., after the fourth programming content segment only. With reference to the second use case 626 of the third exemplary scenario 600C in FIG. 6C, the SSAI system 109 may generate the updated pre-encoded media asset manifest, i.e., Manifest 2, that comprises the additional programming content segments, such as PS 6 and PS Last.

At 758, in the additional time duration, the insertion of the non-scheduled programming content and/or the non-programming content in the updated pre-encoded media asset manifest may be completed at a portion of or an entire first set of content placement opportunities defined in the metadata. In accordance with an embodiment, the SSAI system 109 may be configured to complete the insertion of the non-scheduled programming content and/or the non-programming content in the updated pre-encoded media asset manifest at a portion of or an entire first set of content placement opportunities defined in the metadata. The insertion may be completed in the additional time duration. For example, in absence of any marking in the pre-encoded media asset manifest or external data, such as metadata, indicting the location of skippable items, such as opening credits, or a recap of previous episodes, the updated pre-encoded media asset manifest may include sufficient programming content segments to provide the SSAI system 109 some more time to complete the insertion of the advertisements for the defined break locations in the final pre-encoded media asset manifest.

With reference to the second use case 606 of the first exemplary scenario 600A in FIG. 6A, the SSAI system 109 may complete the insertion of the non-programming content, such as NPS 1, . . . , NPS 3, and NPS 4, . . . , NPS 6, in the updated pre-encoded media asset manifest, such as Manifest 2, at the first set of content placement opportunities, such as locations L1 and L2, respectively, defined in the metadata.

In an example, with reference to the first use case 624 of the third exemplary scenario 600C in FIG. 6C, the SSAI system 109 may complete the insertion of the non-programming content, such as NPS 1, . . . , NPS 3, in the updated pre-encoded media asset manifest, such as Manifest 2, at a portion of the first set of content placement opportunities, such as location L1, defined in the metadata. With reference to the second use case 626 of the third exemplary scenario 600C in FIG. 6C, the SSAI system 109 may complete the insertion of the non-programming content, such as NPS 1, . . . , NPS 3, and NPS 4, . . . , NPS 6, in the updated pre-encoded media asset manifest, such as Manifest 2, at the first set of content placement opportunities, such as locations L1 and L2, respectively, defined in the metadata.

At 760, an updated pre-encoded media asset manifest may be communicated to the first client device in response to an updated manifest request. In accordance with an embodiment, the SSAI system 109 may be configured to communicate the updated pre-encoded media asset manifest to the first client device, such as the client device 132 a, in response to the updated manifest request. For example, with reference to the first use cases 604, 614, and 624 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, Manifest 2 may be communicated to the first client device, such as the client device 132 a. Similarly, with reference to the second use cases 606, 616, and 626 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, Manifest 2 may be communicated to the first client device, such as the client device 132 a.

At 762, the updated pre-encoded media asset manifest may be designated to inform the media player of the first client device to generate the subsequent manifest request or the final manifest request. In accordance with an embodiment, the SSAI system 109 may be configured to designate the updated pre-encoded media asset manifest to inform the media player of the first client device, such as the client device 132 a, to generate the subsequent manifest request or the final manifest request. The updated pre-encoded media asset manifest may continue to be designated to inform the media player of the first client device, such as the client device 132 a, of a need to request updated pre-encoded media asset manifest as if it were a live or event stream.

In an example, with reference to the first use cases 604, 614, and 624 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, the SSAI system 109 may designate the updated pre-encoded media asset manifest, i.e., Manifest 2, to inform the media player of the first client device, such as the client device 132 a, to generate the subsequent manifest request or a final manifest request. In another example, with reference to the second use cases 606, 616, and 626 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, the SSAI system 109 may designate the updated pre-encoded media asset manifest, i.e., Manifest 2, to inform the media player of the first client device, such as the client device 132 a, to generate the subsequent manifest request. In both the examples above, the subsequent manifest request may correspond to generation of the subsequent manifest request or a final manifest request.

Such cycle is continually repeated and the control passes back to operation 740 in flowchart 700D until the final pre-encoded media asset manifest with the non-scheduled programming content and/or the non-programming content can be generated based on the defined criteria and the final pre-encoded media asset manifest is communicated to the first client device, such as the client device 132 a. For example, at 740, with reference to the second use cases 606, 616, and 626 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, the SSAI system 109 may determine that the insertion of the non-programming content is complete and the defined criteria is met. Thus, the SSAI system 109 may generate the final pre-encoded media asset manifests corresponding to Manifest 2, communicate the final pre-encoded media asset manifests to the client device 132 a, designate the final pre-encoded media asset manifests to inform the client device 132 a to cease further generation of subsequent requests, and store the initial, updated and the final pre-encoded media asset manifests for designated period of time. However, at 740, with reference to the first use cases 604, 614, and 624 of the first exemplary scenario 600A, the second exemplary scenario 600B, and the third exemplary scenario 600C, respectively, the SSAI system 109 may determine that the insertion of the non-programming content is incomplete and the defined criteria is not met. Thus, control passes to the operation at 750 to repeat the generation of updated pre-encoded media asset manifests until the insertion of the non-programming content is complete and the defined criteria is met.

Various embodiments of the disclosure comprise the media packaging and distribution system 102 that may be configured to publish disparate live media output streams to be viewed on a plurality of consumer devices (such as the consumer devices 110 a, . . . , 110 n) based on user selection. The media packaging and distribution system 102 may comprise, for example, the DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine 114, PEM 115, indexing and storage system 116, the stream selection service 142, and the repository of schedules, rights, and user preferences database 144. In accordance with an embodiment, one or more processors in the DACIS 103 may be configured to receive a first manifest request, comprising one or more parameters, from a first client device, such as client device 132 a. The one or more processors in the DACIS 103 may be further configured to determine a first additional content comprising a customized first programming content and a targeted first non-programming content for the first client device based on the one or more parameters and associated indexed metadata retrieved based on the one or more parameters. The one or more processors in the DACIS 103 may be further configured to generate the first programming schedule 111, for the first client device based on selected one or more live input stream and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content. The one or more processors in the DACIS 103 may be further configured to select one or more live input stream manifests and/or one or more pre-encoded media asset manifests published in the content delivery system 130 and associated indexed metadata based on the one or more parameters. The one or more processors in the DACIS 103 may be further configured to publish a first disparate live media output stream manifest for the first client device based on insertion of the selected one or more live input stream manifests and/or the one or more pre-encoded media asset manifests, the associated indexed metadata, and the determined first additional content in accordance with the first programming schedule 111, generated for the first client device.

In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to index a plurality of media segments indicated by the one or more pre-encoded media asset manifests and the one or more live input stream manifests, the associated indexed metadata, the targeted first non-programming content, and the customized first programming content based on the first programming schedule 111 generated for the first client. In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to insert the first additional content at one or more content placement opportunities indicated in the first disparate live media output stream manifest based on the first programming schedule 111 generated for the first client device. The one or more content placement opportunities may be defined by the metadata associated with the one or more live input streams corresponding to the one or more live input stream manifests and/or one or more pre-encoded media assets corresponding to the one or more pre-encoded media asset manifests. The insertion of the targeted first non-programming content and the customized first programming content in real time, the associated indexed metadata and/or the one or more content placement opportunities may include programming content indicators, non-programming content indicators, graphical treatment indicators, and interactive content indicators.

In accordance with an embodiment, the insertion of the customized first programming content, in an instance in which the generated first disparate live media output stream manifest corresponds to a disparate live media output stream, a first set of processors in the DACIS 103 may be further configured to receive universal resource locators and/or identifiers referencing records for the selected one or more live input streams and/or the one or more pre-encoded media assets from the CPDS 107. The associated indexed metadata and/or one or more content placement opportunities may include programming content indicators, non-programming content indicators, graphical treatment indicators, and interactive content indicators. The programming content indicators may comprise a plurality of categories for the customized first programming content.

In accordance with an embodiment, the first set of processors in the DACIS 103 may be further configured to transmit a request to the CDS 105 for determining the customized first programming content from a content package and distribution system for matching one or more personalization parameters. The one or more personalization parameters may include user preferences and identifiers from the first manifest request or retrieved from the repository of schedules, rights, and user preferences database 144, and time constraints. The time constraints may be determined based on user preferences retrieved from the repository of schedules, rights, and user preferences database 144, a range defined in the first manifest request, and schedule tolerances defined in the repository of schedules, rights, and user preferences database 144, client device preferences or identifiers from the first manifest request or retrieved from the repository of schedules, rights, and user preferences database 144, geolocation information from the first manifest request or retrieved from the repository of schedules, rights, and user preferences database 144, and/or a content recommendation engine.

In accordance with an embodiment, the one or more parameters may comprise universal resource locators and/or identifiers referencing records for one or more live input streams or one or more pre-encoded media assets in the CPDS 107, a plurality of client-specific parameters, and a plurality of client-specified attributes derived from a user interaction with the first client device. The plurality of client-specific parameters may comprise user preferences and identifiers, client device preferences and identifiers, and one or more rules governed by geolocation data and current position of playback of a first disparate live media output stream at the first client device. In accordance with an embodiment, for the insertion of the targeted first non-programming content, the plurality of client-specified attributes may comprise the user interaction with interactive content in the customized first programming content and the targeted first non-programming content, and a preference for a type and/or category of the targeted first non-programming content and/or the customized first programming content. The user interaction with the interactive content comprises a selection to exclude the targeted first non-programming content and/or the customized first programming content, a selection to include a subset of the targeted first non-programming content and/or the customized first programming content, and a selection to include all of the targeted first non-programming content and/or the customized first programming content within one or more specified non-programming content locations. The targeted first non-programming content may comprise personalized advertisements including video advertisements, graphical treatment, cue points, and the interactive content comprising a set of interactive elements for the targeted first non-programming content. The customized first programming content may comprise personalized non-advertising content including promotional content, a short-form content, and an alternate additional content for replacement of at least a portion of a first disparate live media output stream generated for the first client.

In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to transmit the published first disparate live media output stream manifest to a media player of the first client device for a playback of a first disparate live media output stream. The media player, during playback of the first disparate live media output stream at the first client device, may present one or more decision points defined by the interactive content to initiate a user interaction at the first client device. At the one or more decision points, the user interaction may correspond to one of a desired selection corresponding to the user interaction with one or more interactive elements, or a default selection corresponding to non-interaction of a user with the customized first programming content and/or the targeted first non-programming content in the first disparate live media output stream played back by the media player. The desired selection or the default selection may be transmitted to an external storage system that is the repository of schedules, rights, and user preferences database 144. At the one or more decision points, the one or more interactive elements may be configured to exclude the targeted first non-programming content or the customized first programming content and be replaced by default content, select alternate customized first programming content, select a subsequent second programming content, approve or disapprove selected customized first programming content, exclude subsequent second non-programming content for a remaining portion of the first disparate live media output stream played back by the media player, select one or more targeted first non-programming content of a specific category, or view some or all of the targeted first non-programming content immediately to avoid some or all of the targeted first non-programming content for the remaining portion of the first disparate live media output stream played back by the media player.

In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to modify a remaining portion of the first programming schedule 111 that generates first disparate live media output stream corresponding to the first manifest request generated by the first client device based on the user interaction with the interactive content. A first set of processors in the DACIS 103 may be configured to receive the first manifest request from a second set of processors in the DACIS 103, select, based on the received first manifest request, one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144, and transmit universal resource locators and/or identifiers referencing records for the selected one or more live input streams and/or the one or more pre-encoded media assets to the second set of processors in the DACIS 103.

In accordance with an embodiment, the second set of processors in the DACIS 103 may be further configured to retrieve the indexed metadata associated with the selected one or more live input streams and/or the one or more pre-encoded media assets from the CPDS 107. The associated indexed metadata may define one or more content placement opportunities within the selected one or more live input streams and/or the one or more pre-encoded media assets. The customized first programming content and the targeted first non-programming content may be identified as the first additional content to be scheduled at the one or more content placement opportunities based on the one or more parameters in the received first manifest request and the associated indexed metadata, wherein the generated first programming schedule 111 excludes the first additional content or includes the first additional content completely or partially.

In accordance with an embodiment, a third set of processors in the DACIS 103 may be further configured to insert, based on the generated first programming schedule 111, the identified customized first programming content and the targeted first non-programming content into the first disparate live media output stream manifest in accordance with the one or more content placement opportunities defined in the associated indexed metadata and one or more rules and conditions defined in the repository of schedules, rights, and user preferences database 144. The identification of the targeted first non-programming content may be based on execution of a non-programming content service based on rules and conditions defined in additional parameters of the repository of schedules, rights, and user preferences database 144, and the one or more parameters defined in the first manifest request. The identification of the customized first programming content may be based on execution of the CDS 105 based on the rules and conditions defined in the additional parameters of the repository of schedules, rights, and user preferences database 144. In accordance with an embodiment, the first programming schedule 111 may define locations and types of one or more decision points defined by one or more content placement opportunities in the indexed metadata. In an instance when one or more pre-encoded media assets are being scheduled and the one or more decision points defined by the one or more content placement opportunities are to be inserted in the first programming schedule 111, the first programming schedule 111 may be configured to control the one or more pre-encoded media asset manifests to be published as the first disparate live media output stream manifest.

In accordance with an embodiment, a conversion of one or more pre-encoded media assets into a first disparate live media output stream facilitates one or more subsequent modifications on the first disparate live media output stream. The one or more subsequent modifications may correspond to a user selection, a user preference, a change in the first programming schedule 111, or a time or geolocation-based rule.

In accordance with an embodiment, the first set of processors in the DACIS 103 may be further configured to transmit universal resource locators and/or identifiers referencing records for the selected one or more live input streams and/or the one or more pre-encoded media assets to the second set of processors. In an absence of one or more live input streams, the first set of processors may be configured to select a pre-encoded asset indicated in the first manifest request to continue playback as the first disparate live media output stream. The second set of processors may be configured to select a second disparate live media output stream according to accessibility of the first disparate live media output stream. The first disparate live media output stream is not updated and/or the first disparate live media output stream has media and/or a manifest that is incompatible with a client request. The second set of processors may be further configured to select the second disparate live media output stream according to rules provided by a stream owner/operator and user preferences defined in the repository of schedules, rights, and user preferences database 144.

In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to transition from the first additional content to an alternate additional content based on one or more transition parameters. The one or more transition parameters may comprise one or more parameters from the first manifest request, current state of the first disparate live media output stream manifest determined based on accessibility, regular update, and suitable encoding, digital rights management, and compatibility with the first client device, rules provided by a stream owner operator, and user preferences defined in the repository of schedules, rights, and user preferences database 144.

In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to retrieve alternate metadata for the alternate additional content from the CPDS 107. The alternate metadata may indicate a location to transition from the first additional content to the alternate additional content. The one or more processors may be further configured to determine placement of the alternate additional content within the first disparate live media output stream manifest based on the associated indexed metadata and the alternate metadata. The one or more processors may be further configured to generate the alternate programming schedule 113, for the first client device based on the alternate additional content and the alternate metadata, and transmit the generated alternate programming schedule to the first set of processors. The first set of processors may be configured to generate a final disparate live output stream manifest for the first client device. In accordance with an embodiment, another conversion of the first disparate live media output stream into the one or more pre-encoded media assets facilitates download of the one or more pre-encoded media assets at the first client device and mitigates dependency on the system for playback of remaining portion. In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to receive a request from the first client device, wherein the request comprises the one or more parameters. The one or more processors in the DACIS 103 may be further configured to determine alternate additional content for inclusion in the first disparate live media output stream manifest or replacement of the first additional content in the first disparate live media output stream manifest based on the one or more parameters. The one or more processors in the DACIS 103 may be further configured to modify the first programming schedule 111 to generate an alternate programming schedule for the first client device based on the alternate additional content and associated metadata. The one or more processors in the DACIS 103 may be further configured to transmit the generated alternate programming schedule to a second set of processors, wherein the second set of processors is configured to generate a final disparate live output stream manifest for the first client device.

In accordance with an embodiment, the one or more processors in the DACIS 103 may be further configured to revoke the first disparate live media output stream manifest published for the first client device based on an identifier primitive associated with the first disparate live media output stream of the first client device in an instance in which a media player of the first client device is determined to be a plagiarized media player. The first disparate live media output stream may include at least one unique identifier inserted by the one or more processors in the DACIS 103.

In accordance with various embodiments, the first disparate live media output stream manifest for the first client device may be generated based on one of a pre-defined conversion modes. The pre-defined conversion modes may correspond to pre-encoded media assets to live stream mode, pre-encoded media assets to live stream mode with scalable architecture, a live stream to live stream mode, and a mixed mode corresponding to switching between pre-encoded media assets and live streams.

In accordance with an embodiment, one or more processors in the PEM 115 may be configured to receive a first manifest request, comprising one or more parameters, from the first client device. Further, the received first manifest request may be transmitted to a first set of processors in the stream selection service 142. The first set of processors may be configured to select, based on the received first manifest request, one or more live input streams and/or one or more pre-encoded media assets based on the one or more parameters and additional parameters retrieved from the repository of schedules, rights, and user preferences database 144. The one or more processors in the PEM 115 may be configured to receive universal resource locators and/or identifiers referencing records for the selected one or more live input streams and/or the one or more pre-encoded media assets from the first set of processors. The one or more processors in the PEM 115 may be configured to retrieve indexed metadata associated with the selected one or more live input streams and/or the one or more pre-encoded media assets from a content packaging and distribution system, wherein the indexed metadata defines one or more content placement opportunities within the selected one or more live input streams and/or the one or more pre-encoded media assets. The one or more processors in the PEM 115 may be further configured to identify a customized first programming content and a targeted first non-programming content as a first additional content to be scheduled in the one or more content placement opportunities based on the one or more parameters in the received first manifest and the associated indexed metadata. The one or more processors in the PEM 115 may be further configured to generate the first programming schedule 111 for the first client device based on the associated indexed metadata, the first additional content and the one or more live input streams and/or one or more pre-encoded media assets.

Various embodiments of the disclosure comprise the media packaging and distribution system 102 that may be configured to manage a pre-encoded media asset for immediate playback. The media packaging and distribution system 102 may comprise one or more processors, for example, the CDS 105, the CPDS 107, the content encoder/packager 107 a, the content metadata store 107 b, the SSAI system 109, the internal manifest index 109 a, and the repository of schedules, rights, and user preferences database 144. The one or more processors in the media packaging and distribution system 102 may be implemented in conjunction with the Ad decisioning servers 106 a, . . . , 106 n, the external data source 120, the content delivery system 130, and the client devices 132 a, . . . , 132 n. In accordance with an embodiment, one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to generate, based on a receipt of an initial manifest request from a first client device, such as the client device 132 a, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments. The one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be further configured to communicate the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device, such as the client device 132 a, via a content delivery system, such as the content delivery system 130, for an immediate playback of a pre-encoded media asset, such as the first pre-encoded media asset 602, the second pre-encoded media asset 612, and the third pre-encoded media asset 622. The one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be further configured to assign a unique SID to the first client device, such as the client device 132 a, to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request. The one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be further configured to generate a final pre-encoded media asset manifest, such as Manifest 3 as illustrated in both the use cases of the first exemplary scenario 600A, the second exemplary scenario 600B, the third exemplary scenario 600C, upon a receipt of the subsequent manifest request from the first client device, such as the client device 132 a, based on a defined criterion. The final pre-encoded media asset manifest may comprise remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the content encoder/packager 107 a, may be configured to generate the pre-encoded media asset comprising a plurality of programming content segments for the distribution. The one or more processors in the media packaging and distribution system 102, such as the content encoder/packager 107 a, may be further configured to adjust, based on metadata retrieved from a content metadata store, such as the content metadata store 107 b, the plurality of programming content segments in the pre-encoded media asset. The adjustment of the plurality of programming content segments may provide a first set of content placement opportunities where the non-scheduled programming content and/or the non-programming content are inserted in a pre-encoded media asset manifest. The adjustment of the plurality of programming content segments may provide a second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest. The first set of content placement opportunities may correspond to programming indicators and non-programming indicators and the second set of content placement opportunities correspond to event markers. The non-scheduled programming content may correspond to additional content provided by a content decision server, the non-programming content may correspond to advertisement breaks or promotional content provided by an advertisement decision server, and the event-based programming content may correspond to an identifier corresponding to an event related to content of the pre-encoded media asset

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the content encoder/packager 107 a, may be configured to store timestamps of the first set of content placement opportunities and the second set of content placement opportunities in the metadata upon the generation of the pre-encoded media asset.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the content encoder/packager 107 a, may be configured to mark a start location and an end location of each of the first set of content placement opportunities and the second set of content placement opportunities in the pre-encoded media asset manifest.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to receive an initial manifest request from the first client device, such as the client device 132 a, to view the pre-encoded media asset. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102 may be configured to access the pre-encoded media asset manifest, based on the received initial manifest request, from a content delivery system, such as the content delivery system 130, or an internal manifest index, such as the internal manifest index 109 a. Exemplary targeting and non-targeting parameters may include, but are not limited to, metadata associated with the pre-encoded media asset, data associated with the first client device, such as the client device 132 a, and/or data associated with a scheduling window of the pre-encoded media asset.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to, based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules, insert each non-scheduled programming content and/or non-programming content in the pre-encoded media asset manifest as an initial and final response to the initial manifest request for playback of the pre-encoded media asset at the first client device, such as the client device 132 a, in accordance with a first instruction. In accordance with an embodiment, the initial pre-encoded media asset manifest may be independent of the non-scheduled programming content and/or the non-programming content. In accordance with an embodiment, the initial pre-encoded media asset manifest may be based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules. In accordance with an embodiment, the initial pre-encoded media asset manifest may enable the immediate playback of the pre-encoded media asset at the first client device in accordance with a second instruction.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to determine a capability of the first client device, such as the client device 132 a, based on the targeting and/or non-targeting parameters, the external system and/or the set of pre-determined rules. The capability of the first client device, such as the client device 132 a, corresponds to an extent of player integration with the system and compatibility of the first client device, such as the client device 132 a, with a required protocol.

In accordance with an embodiment, in case the extent of the player integration with the system is limited and the first client device, such as the client device 132 a, is incompatible with the required protocol, size of the initial set of programming content segments is verified to be equal to a capacity of a playback buffer in the media player of the first client device, such as the client device 132 a. The equality between the size of the initial set of programming content segments and the capacity of the playback buffer facilitates the immediate playback at the first client device, such as the client device 132 a, from beginning of the pre-encoded media asset.

In accordance with an embodiment, in case the extent of the player integration with the system is complete and the first client device, such as the client device 132 a, is compatible with the required protocol, the initial pre-encoded media asset manifest may comprise the initial set of programming content segments up to a first content placement opportunity from the first set of content placement opportunities marked for insertion of a first non-scheduled programming content and/or non-programming content. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to communicate a signal to the media player of the first client device, such as the client device 132 a, to start the immediate playback from beginning of the pre-encoded media asset. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to control a timing of the subsequent manifest request to be generated by the media player of the first client device, such as the client device 132 a. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to provide data indicating a duration of the pre-encoded media asset to the media player of the first client device, such as the client device 132 a.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to designate the initial pre-encoded media asset manifest to inform the media player of the first client device, such as the client device 132 a, to generate the subsequent manifest request.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to verify receipt of information regarding each of the non-scheduled programming content and/or the non-programming content from corresponding servers, such as the CDS 105 and the Ad decisioning servers 106 a, . . . , 106 n. The one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to determine whether insertion of each of the non-scheduled programming content and/or the non-programming content is complete or incomplete in an updated pre-encoded media asset manifest based on the received information.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to communicate the final pre-encoded media asset manifest to the first client device, such as the client device 132 a, in response to the subsequent manifest request when the defined criterion is met. The defined criterion may correspond to the determination that the insertion of the non-scheduled programming content and/or the non-programming content in the final pre-encoded media asset manifest is complete. The final pre-encoded media asset manifest may include references to the set of non-scheduled programming content segments and/or non-programming content segments corresponding to each non-scheduled programming content and/or non-programming content respectively, inserted at a first set of content placement opportunities defined in metadata. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to designate the final pre-encoded media asset manifest to inform the media player of the first client device, such as the client device 132 a, to cease further generation of the subsequent manifest request.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to communicate the updated pre-encoded media asset manifest to the first client device, such as the client device 132 a, in response to an updated manifest request. The updated pre-encoded media asset manifest may be generated when the insertion of the non-scheduled programming content and/or the non-programming content is determined to be incomplete. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to designate the updated pre-encoded media asset manifest to inform the media player of the first client device, such as the client device 132 a, to generate the subsequent manifest request or the final manifest request.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to add additional content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments and/or non-programming content segments in the updated pre-encoded media asset manifest to provide additional time duration. In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to complete, in the additional time duration, the insertion of the non-scheduled programming content and/or the non-programming content in the updated pre-encoded media asset manifest at a portion of or an entire first set of content placement opportunities defined in metadata when the pre-encoded media asset manifest and/or the metadata does not include a second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to add a plurality of event-based programming content segments and additional content segments in the updated pre-encoded media asset manifest when the pre-encoded media asset manifest and/or metadata includes a second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest. The size of the additional content segments may match with capacity of a playback buffer in the media player of the first client device, such as the client device 132 a.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to allow the media player of the first client device, such as the client device 132 a, to begin the immediate playback after a marked end location of the plurality of event-based programming content segments upon receipt of an input from the first client device, such as the client device 132 a, to skip the event-based programming content. The immediate playback starts from a beginning of the additional content segments in the updated pre-encoded media asset manifest.

In accordance with an embodiment, the one or more processors in the media packaging and distribution system 102, such as the SSAI system 109, may be configured to store the initial, the updated, and/or the final pre-encoded media asset manifests as a set of asset manifests corresponding to the unique SID for a designated period of time when the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content is verified, the insertion of each of the non-scheduled programming content and/or the non-programming content is determined to be complete, and the final pre-encoded media asset manifest is communicated to the first client device, such as the client device 132 a. The set of asset manifests is stored based on duration of the pre-encoded media asset upon receipt of a request of a different profile from the media player of the first client device, such as the client device 132 a, based on connectivity changes of the first client device.

In accordance with an embodiment, the initial pre-encoded media asset manifest may be communicated as the first disparate live media output stream manifest to the first client device, such as the client device 132 a, based on one of a pre-defined conversion modes. The pre-defined conversion modes correspond to a pre-encoded media assets to live stream mode or a pre-encoded media assets to live stream mode with scalable architecture. The conversion facilitates a subsequent modification to the first disparate live media output stream. The subsequent modification corresponds to one of a user selection, a user preference, or a change in a time or geolocation-based rule.

Various embodiments of the disclosure may provide a computer-readable medium, such as the non-transitory computer-readable medium 506, having stored thereon, computer implemented instruction that when executed by the processor 504 causes the media packaging and distribution system 102 to execute operations for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content. In accordance with an embodiment, the processor 504 causes the media packaging and distribution system 102 to execute operations to receive a first manifest request, comprising one or more parameters, from a first client device, such as client device 132 a. The processor 504 causes the media packaging and distribution system 102 to execute operations to determine a first additional content comprising a customized first programming content and a targeted first non-programming content for the first client device based on the one or more parameters and associated indexed metadata retrieved based on the one or more parameters. The processor 504 causes the media packaging and distribution system 102 to execute operations to generate the first programming schedule 111, for the first client device based on selected one or more live input stream and/or the one or more pre-encoded media assets, the associated indexed metadata, and the determined first additional content. The processor 504 causes the media packaging and distribution system 102 to execute operations to select one or more live input stream manifests and/or one or more pre-encoded media asset manifests published in the content delivery system 130 and associated indexed metadata based on the one or more parameters. The processor 504 causes the media packaging and distribution system 102 to execute operations to publish a first disparate live media output stream manifest for the first client device based on insertion of the selected one or more live input stream manifests and/or the one or more pre-encoded media asset manifests, the associated indexed metadata, and the determined first additional content in accordance with the first programming schedule 111, generated for the first client device.

Various embodiments of the disclosure may provide a computer-readable medium, such as the non-transitory computer-readable medium 556, having stored thereon, computer implemented instruction that when executed by the processor 554 causes the media packaging and distribution system 102 to execute operations for managing a pre-encoded media asset for immediate playback. In accordance with an embodiment, the processor 554 causes the media packaging and distribution system 102 to execute operations to generate, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments. The processor 554 further causes the media packaging and distribution system 102 to execute operations to communicate the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device, such as the client device 132 a, via a content delivery system, such as the content delivery system 130, for an immediate playback of a pre-encoded media asset, such as the first pre-encoded media asset 602, the second pre-encoded media asset 612, and the third pre-encoded media asset 622. The processor 554 further causes the media packaging and distribution system 102 to execute operations to assign a unique SID to the first client device, such as the client device 132 a, to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request. The processor 554 further causes the media packaging and distribution system 102 to execute operations to generate a final pre-encoded media asset manifest, such as Manifest 3 as illustrated in both the use cases of the first exemplary scenario 600A, the second exemplary scenario 600B, the third exemplary scenario 600C, upon a receipt of the subsequent manifest request from the first client device, such as the client device 132 a, based on a defined criterion. The final pre-encoded media asset manifest may comprise remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters.

Existing systems for SSAI support live streaming and make decisions to insert non-programing content in near real-time. However, for On-Demand streaming, such decisions to insert non-programing content are made upfront. Accordingly, amount of control the user can excerpt to influence what non-programming content is shown may get limited. Further, newer ad models are developing that rely less on interruptive video advertising and more on contextual based graphical treatment advertising within the program content. To this extent, SSAI systems have been able to circumvent ad blockers by requesting video ads on behalf of the client device and stitching them into the disparate live media output stream manifest.

To address at least the above problems, in accordance with the various embodiments of the present disclosure, the DACIS 103 in the media packaging and distribution system 102 may be configured to include not showing non-programming content that the user elected to skip or rated poorly in an earlier non-programming content break, or could enable the user to skip all non-programming content because the user interacted with an previous non-programming content or made a purchase and the advertiser elected to sponsor the remainder of the program.

The DACIS 103 may notified about graphical treatment opportunities within the content, make the necessary ad calls on behalf of the client device, and provide the client device with the information needed to execute the overlays via a secure out-of-band channel between the DACIS 103 and the client device. In many cases, a channel already exists to support passing the program indicators, such as start and end information, to the client device and Video Player Ad-Serving Interface (VPAID) ads that cannot be stitched.

DACIS 103 may also provide an opportunity to leverage the 1:1 scale of traditional SSAI systems to support custom content choices and not just targeted advertising. For example, when a user selects to join a live stream, the CDS 105 coupled with the DACIS 103 may determine that, instead of joining the live stream for the last few minutes of a program, the user should instead be shown content more relevant to the next program. For example, showing a personalized set of basketball highlights and ads to a user who likely joined the stream to watch the basketball game that is coming on next.

Further, the DACIS 103 may be used to provide seamless failover between redundant streams for large events, thus improving reliability. While some client devices support primary and backup streams and are able to fail between them, many client devices do not. In such cases, the client device may attempt to join the alternative stream after occurrence of an event, such as a device failure or crash. For such clients, the DACIS 103 monitors both the primary and backup stream, and if there is a failure, inserts the alternative stream into the output manifest. Thus, the media packaging and distribution system 102 provides an enhanced, intelligent, and personalized viewer experience with increased appeal in order to retain and gain a wider audience.

The DACIS 103, the CDS 105, the CPDS 107, the stream publishing engine 114, PEM 115, indexing and storage system 116, the stream selection service 142, and the repository of schedules, rights, and user preferences database 144 in conjunction with each other, provide significant productivity and efficiency improvements since the process of generating disparate live media output streams with additional content is specific to each consumer device. The disparate live media output streams are simplified as the generated disparate live media output streams are independent of a requirement to re-process, that is re-encode and re-package, various live input streams for media distribution to the plurality of consumer devices in real time or near-real time. Thus, the network provider now may provide live channel offerings in a cost-effective manner.

Various components, as described above in FIG. 1B, enable the media packaging and distribution system 102 to leverage the modern streaming protocols, based on which the media packaging and distribution system 102 generates disparate live media output streams of the live broadcast channels with additional content and one or more decision points to influence the remaining disparate live media output streams. The disparate live media output streams may be generated based on insertion of live input streams into a generated disparate live media output stream using pre-encoded media assets. In this regard, manifests from the live input streams and the pre-encoded media assets may be manipulated and produced for distribution of the disparate live media output stream.

As the media content itself does not need to be processed beyond the initial creation of the live input streams and pre-encoded media assets prepared for distribution, it is extremely inexpensive to provide such disparate live media output streams and alternate disparate live media output stream (in case of stream failover). It may be based solely on the cost to manipulate the manifests, which provide the instructions for the media players in the client devices 132 a, . . . , 132 n to execute. The media packaging and distribution system 102 may also support targeted ad insertion and customized programming content insertion on a per client basis and may further leverage the processing power of the individual client devices 132 a, . . . , 132 n to insert targeted channel graphics and graphical treatment advertisements and promotions.

Various other components, as described above in FIG. 1D, may enable the media packaging and distribution system 102 to leverage the salient features of modern web streaming protocols and capabilities of the media players in client devices to manage corresponding video buffers in such a manner that the media players are allowed to access the first segment of the pre-encoded media asset, such as VOD asset, in minimal time for immediate playback. At the same time, for the whole duration of the pre-encoded media asset, the media packaging and distribution system 102 does not introduce the cost of sustaining (or maintaining) a client session. Thus, the proposed system and method in the media packaging and distribution system 102 is high on cost saving as compared to existing systems and methods and provides a seamless viewer experience by mitigating the delay in delivering the asset manifest of the pre-encoded media asset to the media players. It also simplifies the user experience by supporting trick play modes with given extent of player-SSAI system integration.

More specifically, to ensure a smooth video playback of the pre-encoded media asset, the client device downloads and buffers a few video segments (typically 3) before the video playback. For an older client device that extends limited SSAI integration and is incompatible with required protocols, an initial pre-encoded media asset manifest may be generated with the number of segments equivalent to the video buffer. While the client device downloads such segments and begins playback, ads may be inserted in the remaining manifest. When the client device requests an updated manifest, the entire playlist stitched with ads may be provided in response, if all the ads are inserted. If the ads are still being inserted, additional segments may be added to the updated manifest and returned to the client device. Upon the subsequent manifest request for the updated manifest, the entire playlist stitched with ads may be returned. The advantage of the proposed approach is that the client session is typically less than 30 seconds, versus the duration of the VOD asset. Further, trick mode control by the client device may be enabled as soon as the entire manifest is delivered, without the need for complex player integration.

Further, enabling the viewer's capability to skip previous episode recaps and opening credits may also be maintained, with additional intelligence and knowledge of the SSAI system 109 about how such events are identified. A manifest inclusive of the event-based programming segments of the skippable portion of the content along with the additional content segments equivalent to the video buffer of the media player may be returned, in response to the media player request after the playback is started.

As utilized herein the terms “circuits” and “circuitry” refer to physical electronic components (for example, hardware) and any software and/or firmware (“code”) which may configure the hardware, be executed by the hardware, and/or otherwise be associated with the hardware. As used herein, for example, a particular processor and memory may comprise a first “circuit” when executing first one or more lines of code and may comprise a second “circuit” when executing second one or more lines of code. As utilized herein, “and/or” means any one or more of the items in the list joined by “and/or”. As an example, “x and/or y” means any element of the three-element set {(x), (y), (x, y)}. As another example, “x, y, and/or z” means any element of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z), (x, y, z)}. As utilized herein, the term “exemplary” means serving as a non-limiting example, instance, or illustration. As utilized herein, the terms “e.g.,” and “for example” set off lists of one or more non-limiting examples, instances, or illustrations. As utilized herein, circuitry is “operable” to perform a function whenever the circuitry comprises the necessary hardware and/or code (if any is necessary) to perform the function, regardless of whether performance of the function is disabled, or not enabled, by some user-configurable setting.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of embodiments of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “includes” and/or “including”, when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Further, many embodiments are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, these sequences of actions described herein can be considered to be embodied entirely within any non-transitory form of computer readable storage medium having stored therein a corresponding set of computer instructions that upon execution would cause an associated processor to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the embodiments described herein, the corresponding form of any such embodiments may be described herein as, for example, “logic configured to” perform the described action.

Another embodiment of the disclosure may provide a non-transitory machine and/or computer readable storage and/or media, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform the steps as described herein for publishing a disparate per-client live media output stream based on dynamic insertion of targeted non-programming content and customized programming content, and for managing a pre-encoded media asset for immediate playback.

The present disclosure may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, either statically or dynamically defined, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.

Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, algorithms, and/or steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, firmware, or combinations thereof. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The methods, sequences and/or algorithms described in connection with the embodiments disclosed herein may be embodied directly in firmware, hardware, in a software module executed by a processor, or in a combination thereof. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, physical and/or virtual disk, a removable disk, a CD-ROM, virtualized system or device such as a virtual servers or container, or any other form of storage medium known in the art. An exemplary storage medium is communicatively coupled to the processor (including logic/code executing in the processor) such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.

While the present disclosure has been described with reference to certain embodiments, it will be noted understood by, for example, those skilled in the art that various changes and modifications could be made and equivalents may be substituted without departing from the scope of the present disclosure as defined, for example, in the appended claims. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. The functions, steps and/or actions of the method claims in accordance with the embodiments of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims. 

What is claimed is:
 1. A system, comprising: memory for storing instructions; and a processor for executing the instructions to perform a method, the method comprising: generating, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments; communicating the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device via a content delivery system for an immediate playback of a pre-encoded media asset; assigning a unique session identifier (SID) to the first client device to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request; and generating a final pre-encoded media asset manifest upon a receipt of the subsequent manifest request from the first client device based on a defined criterion, wherein the final pre-encoded media asset manifest comprises remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters.
 2. The system according to claim 1, wherein the method further comprising: generating the pre-encoded media asset comprising a plurality of programming content segments for distribution; and adjusting, based on metadata retrieved from a content metadata store, the plurality of programming content segments in the pre-encoded media asset, wherein the adjustment of the plurality of programming content segments provides a first set of content placement opportunities where the non-scheduled programming content and/or the non-programming content are inserted in a pre-encoded media asset manifest, wherein the adjustment of the plurality of programming content segments provides a second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest, wherein the first set of content placement opportunities correspond to programming indicators and non-programming indicators and the second set of content placement opportunities correspond to event markers, and wherein the non-scheduled programming content correspond to additional content provided by a content decision server, the non-programming content corresponds to advertisement breaks or promotional content provided by an advertisement decision server, and the event-based programming content corresponds to an identifier corresponding to an event related to content of the pre-encoded media asset.
 3. The system according to claim 2, wherein the method further comprising storing timestamps of the first set of content placement opportunities and the second set of content placement opportunities in the metadata upon the generation of the pre-encoded media asset.
 4. The system according to claim 2, wherein the method further comprising marking a start location and an end location of each of the first set of content placement opportunities and the second set of content placement opportunities in the pre-encoded media asset manifest.
 5. The system according to claim 1, wherein the method further comprising: receiving the initial manifest request from the first client device to view the pre-encoded media asset; and accessing the pre-encoded media asset manifest, based on the received initial manifest request, from a content delivery system or an internal manifest index, wherein the targeting and non-targeting parameters comprise metadata associated with the pre-encoded media asset, data associated with the first client device, and/or data associated with scheduling window of the pre-encoded media asset.
 6. The system according to claim 1, wherein, based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules, the method further comprising inserting each non-scheduled programming content and/or non-programming content in the pre-encoded media asset manifest as an initial and final response to the initial manifest request for playback of the pre-encoded media asset at the first client device in accordance with a first instruction.
 7. The system according to claim 1, wherein the initial pre-encoded media asset manifest is independent of the non-scheduled programming content and/or the non-programming content, wherein the initial pre-encoded media asset manifest is based on the targeting and/or non-targeting parameters, an external system, and/or a set of pre-determined rules, and wherein the initial pre-encoded media asset manifest enables the immediate playback of the pre-encoded media asset at the first client device in accordance with a second instruction.
 8. The system according to claim 7, wherein the method further comprising determining a capability of the first client device based on the targeting and/or non-targeting parameters, the external system and/or the set of pre-determined rules, and wherein the capability of the first client device corresponds to an extent of player integration with the system and compatibility of the first client device with a required protocol.
 9. The system according to claim 8, wherein, in case the extent of the player integration with the system is limited and the first client device is incompatible with the required protocol, size of the initial set of programming content segments is verified to be equal to a capacity of a playback buffer in the media player of the first client device, and wherein the equality between the size of the initial set of programming content segments and the capacity of the playback buffer facilitates the immediate playback at the first client device from beginning of the pre-encoded media asset.
 10. The system according to claim 8, wherein, in case the extent of the player integration with the system is complete and the first client device is compatible with the required protocol, the initial pre-encoded media asset manifest comprises the initial set of programming content segments up to a first content placement opportunity from a first set of content placement opportunities marked for insertion of a first non-scheduled programming content and/or non-programming content, wherein the method further comprising: communicating a signal to the media player of the first client device to start the immediate playback from beginning of the pre-encoded media asset; controlling a timing of the subsequent manifest request to be generated by the media player of the first client device; and providing data indicating a duration of the pre-encoded media asset to the media player of the first client device.
 11. The system according to claim 10, wherein the method further comprising designating the initial pre-encoded media asset manifest to inform the media player of the first client device to generate the subsequent manifest request.
 12. The system according to claim 1, wherein the method further comprising: verifying receipt of information regarding each of the non-scheduled programming content and/or the non-programming content from corresponding servers; and determining whether insertion of each of the non-scheduled programming content and/or the non-programming content is complete or incomplete in an updated pre-encoded media asset manifest based on the information.
 13. The system according to claim 12, wherein the method further comprising: communicating the final pre-encoded media asset manifest to the first client device in response to the subsequent manifest request when the defined criterion is met, wherein the defined criterion corresponds to the determination that the insertion of the non-scheduled programming content and/or the non-programming content in the final pre-encoded media asset manifest is complete, and wherein the final pre-encoded media asset manifest includes references to the non-scheduled programming content segments and/or non-programming content segments corresponding to each non-scheduled programming content and/or non-programming content respectively, inserted at a first set of content placement opportunities defined in metadata; and designating the final pre-encoded media asset manifest to inform the media player of the first client device to cease further generation of the subsequent manifest request.
 14. The system according to claim 12, wherein the method further comprising: communicating an updated pre-encoded media asset manifest to the first client device in response to an updated manifest request, wherein the updated pre-encoded media asset manifest is generated when the insertion of the non-scheduled programming content and/or the non-programming content is determined to be incomplete; and designating the updated pre-encoded media asset manifest to inform the media player of the first client device to generate the subsequent manifest request or the final manifest request.
 15. The system according to claim 14, wherein the method further comprising: adding additional content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments and/or non-programming content segments in the updated pre-encoded media asset manifest to provide additional time duration; and completing, in the additional time duration, the insertion of the non-scheduled programming content and/or the non-programming content in the updated pre-encoded media asset manifest at a portion of or an entire first set of content placement opportunities defined in metadata when the pre-encoded media asset manifest and/or the metadata does not include a second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest.
 16. The system according to claim 14, wherein the method further comprising: adding a plurality of event-based programming content segments and additional content segments in the updated pre-encoded media asset manifest when the pre-encoded media asset manifest and/or metadata includes a second set of content placement opportunities where event-based programming content occurs in the pre-encoded media asset manifest, wherein size of the additional content segments matches with capacity of a playback buffer in the media player of the first client device; and allowing the media player of the first client device to begin the immediate playback after a marked end location of the plurality of event-based programming content segments upon receipt of an input from the first client device to skip the event-based programming content, wherein the immediate playback starts from a beginning of the additional content segments in the updated pre-encoded media asset manifest.
 17. The system according to claim 14, wherein the method further comprising: storing the initial, the updated, and/or the final pre-encoded media asset manifests as a set of asset manifests corresponding to the unique SID for a designated period of time when the receipt of the information regarding each of the non-scheduled programming content and/or the non-programming content is verified, the insertion of each of the non-scheduled programming content and/or the non-programming content is determined to be complete, and the final pre-encoded media asset manifest is communicated to the first client device, wherein the set of asset manifests is stored based on duration of the pre-encoded media asset upon receipt of a request of a different profile from the media player of the first client device based on connectivity changes of the first client device.
 18. The system according to claim 1, wherein the initial pre-encoded media asset manifest is communicated as the first disparate live media output stream manifest to the first client device based on one of a pre-defined conversion modes, wherein the pre-defined conversion modes correspond to a pre-encoded media assets to live stream mode or a pre-encoded media assets to live stream mode with scalable architecture, wherein the conversion facilitates a subsequent modification on the first disparate live media output stream, and wherein the subsequent modification corresponds to one of a user selection, a user preference, or a change in a time or geolocation-based rule.
 19. A method, comprising: generating, at a processor, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments; communicating, by the processor, the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device via a content delivery system for an immediate playback of a pre-encoded media asset; assigning, by the processor, a unique session identifier (SID) to the first client device to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request; and generating, by the processor, a final pre-encoded media asset manifest upon a receipt of the subsequent manifest request from the first client device based on a defined criterion, wherein the final pre-encoded media asset manifest comprises remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters.
 20. A non-transitory computer readable medium, having stored thereon, computer executable code, which when executed by a processor, cause the processor to execute operations, the operations comprising: generating, based on a receipt of an initial manifest request from a first client device, an initial pre-encoded media asset manifest that comprises an initial set of programming content segments; communicating the generated initial pre-encoded media asset manifest, as a first disparate live media output stream manifest, to a media player of the first client device via a content delivery system for an immediate playback of a pre-encoded media asset; assigning a unique session identifier (SID) to the first client device to record a session of the first client device for a subsequent manifest request or a final manifest request associated with the initial manifest request; and generating a final pre-encoded media asset manifest upon a receipt of the subsequent manifest request from the first client device based on a defined criterion, wherein the final pre-encoded media asset manifest comprises remaining programming content segments corresponding to the pre-encoded media asset, non-scheduled programming content segments corresponding to each non-scheduled programming content, and non-programming content segments corresponding to each non-programming content based on targeting and/or non-targeting parameters. 